Search (11 results, page 1 of 1)

0.23988402 = product of:
  0.47976804 = sum of:
    0.06154665 = product of:
      0.18463995 = sum of:
        0.18463995 = weight(_text_:3a in 862) [ClassicSimilarity], result of:
          0.18463995 = score(doc=862,freq=2.0), product of:
            0.32853028 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.03875087 = queryNorm
            0.56201804 = fieldWeight in 862, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.046875 = fieldNorm(doc=862)
      0.33333334 = coord(1/3)
    0.048941493 = weight(_text_:work in 862) [ClassicSimilarity], result of:
      0.048941493 = score(doc=862,freq=4.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.3440991 = fieldWeight in 862, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.046875 = fieldNorm(doc=862)
    0.18463995 = weight(_text_:2f in 862) [ClassicSimilarity], result of:
      0.18463995 = score(doc=862,freq=2.0), product of:
        0.32853028 = queryWeight, product of:
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.03875087 = queryNorm
        0.56201804 = fieldWeight in 862, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.046875 = fieldNorm(doc=862)
    0.18463995 = weight(_text_:2f in 862) [ClassicSimilarity], result of:
      0.18463995 = score(doc=862,freq=2.0), product of:
        0.32853028 = queryWeight, product of:
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.03875087 = queryNorm
        0.56201804 = fieldWeight in 862, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.046875 = fieldNorm(doc=862)
  0.5 = coord(4/8)

Abstract

This research revisits the classic Turing test and compares recent large language models such as ChatGPT for their abilities to reproduce human-level comprehension and compelling text generation. Two task challenges- summary and question answering- prompt ChatGPT to produce original content (98-99%) from a single text entry and sequential questions initially posed by Turing in 1950. We score the original and generated content against the OpenAI GPT-2 Output Detector from 2019, and establish multiple cases where the generated content proves original and undetectable (98%). The question of a machine fooling a human judge recedes in this work relative to the question of "how would one prove it?" The original contribution of the work presents a metric and simple grammatical set for understanding the writing mechanics of chatbots in evaluating their readability and statistical clarity, engagement, delivery, overall quality, and plagiarism risks. While Turing's original prose scores at least 14% below the machine-generated output, whether an algorithm displays hints of Turing's true initial thoughts (the "Lovelace 2.0" test) remains unanswerable.

Source

https%3A%2F%2Farxiv.org%2Fabs%2F2212.06721&usg=AOvVaw3i_9pZm9y_dQWoHi6uv0EN

0.03200227 = product of:
  0.25601816 = sum of:
    0.25601816 = weight(_text_:hochschule in 3141) [ClassicSimilarity], result of:
      0.25601816 = score(doc=3141,freq=2.0), product of:
        0.23689921 = queryWeight, product of:
          6.113391 = idf(docFreq=265, maxDocs=44218)
          0.03875087 = queryNorm
        1.080705 = fieldWeight in 3141, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.113391 = idf(docFreq=265, maxDocs=44218)
          0.125 = fieldNorm(doc=3141)
  0.125 = coord(1/8)

Imprint

Darmstadt : Technische Hochschule / Fb Mathematik

0.028001986 = product of:
  0.22401589 = sum of:
    0.22401589 = weight(_text_:hochschule in 3147) [ClassicSimilarity], result of:
      0.22401589 = score(doc=3147,freq=2.0), product of:
        0.23689921 = queryWeight, product of:
          6.113391 = idf(docFreq=265, maxDocs=44218)
          0.03875087 = queryNorm
        0.9456169 = fieldWeight in 3147, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.113391 = idf(docFreq=265, maxDocs=44218)
          0.109375 = fieldNorm(doc=3147)
  0.125 = coord(1/8)

Imprint

Darmstadt : Technische Hochschule / Fb Mathematik

0.011262473 = product of:
  0.09009978 = sum of:
    0.09009978 = weight(_text_:supported in 2131) [ClassicSimilarity], result of:
      0.09009978 = score(doc=2131,freq=2.0), product of:
        0.22949564 = queryWeight, product of:
          5.9223356 = idf(docFreq=321, maxDocs=44218)
          0.03875087 = queryNorm
        0.3925991 = fieldWeight in 2131, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.9223356 = idf(docFreq=321, maxDocs=44218)
          0.046875 = fieldNorm(doc=2131)
  0.125 = coord(1/8)

Abstract

This is a preprint to be published in the Extensions & Corrections to the UDC. The paper explains the basic functions of browsing and searching that need to be supported in relation to analytico-synthetic classifications such as Universal Decimal Classification (UDC), irrespective of any specific, real-life implementation. UDC is an example of a semi-faceted system that can be used, for instance, for both post-coordinate searching and hierarchical/facet browsing. The advantages of using a classification for IR, however, depend on the strength of the GUI, which should provide a user-friendly interface to classification browsing and searching. The power of this interface is in supporting visualisation that will 'convert' what is potentially a user-unfriendly indexing language based on symbols, to a subject presentation that is easy to understand, search and navigate. A summary of the basic functions of searching and browsing a classification that may be provided on a user-friendly interface is given and examples of classification browsing interfaces are provided.

0.007209763 = product of:
  0.057678103 = sum of:
    0.057678103 = weight(_text_:work in 7953) [ClassicSimilarity], result of:
      0.057678103 = score(doc=7953,freq=2.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.40552467 = fieldWeight in 7953, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.078125 = fieldNorm(doc=7953)
  0.125 = coord(1/8)

Abstract

Describes the work carried out on the TREC-2 project following the results of the TREC-1 project. Experiments were conducted on the OKAPI experimental text information retrieval system which investigated a number of alternative probabilistic term weighting functions in place of the 'standard' Robertson Sparck Jones weighting functions used in TREC-1

0.00576781 = product of:
  0.04614248 = sum of:
    0.04614248 = weight(_text_:work in 3371) [ClassicSimilarity], result of:
      0.04614248 = score(doc=3371,freq=2.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.32441974 = fieldWeight in 3371, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.0625 = fieldNorm(doc=3371)
  0.125 = coord(1/8)

0.005568687 = product of:
  0.044549495 = sum of:
    0.044549495 = product of:
      0.08909899 = sum of:
        0.08909899 = weight(_text_:22 in 3227) [ClassicSimilarity], result of:
          0.08909899 = score(doc=3227,freq=4.0), product of:
            0.13569894 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03875087 = queryNorm
            0.6565931 = fieldWeight in 3227, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=3227)
      0.5 = coord(1/2)
  0.125 = coord(1/8)

Date

7. 2.1996 22:38:41

Pages

22 S

0.004325858 = product of:
  0.034606863 = sum of:
    0.034606863 = weight(_text_:work in 5365) [ClassicSimilarity], result of:
      0.034606863 = score(doc=5365,freq=2.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.2433148 = fieldWeight in 5365, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.046875 = fieldNorm(doc=5365)
  0.125 = coord(1/8)

Abstract

Wikipedia categories, a classification scheme built for organizing and describing Wikpedia articles, are being applied in computer science research. This paper adopts a systematic literature review approach, in order to identify different approaches and uses of Wikipedia categories in information retrieval research. Several types of work are identified, depending on the intrinsic study of the categories structure, or its use as a tool for the processing and analysis of other documentary corpus different to Wikipedia. Information retrieval is identified as one of the major areas of use, in particular its application in the refinement and improvement of search expressions, and the construction of textual corpus. However, the set of available works shows that in many cases research approaches applied and results obtained can be integrated into a comprehensive and inclusive concept of information retrieval.

0.00328138 = product of:
  0.02625104 = sum of:
    0.02625104 = product of:
      0.05250208 = sum of:
        0.05250208 = weight(_text_:22 in 3161) [ClassicSimilarity], result of:
          0.05250208 = score(doc=3161,freq=2.0), product of:
            0.13569894 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03875087 = queryNorm
            0.38690117 = fieldWeight in 3161, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=3161)
      0.5 = coord(1/2)
  0.125 = coord(1/8)

Date

2. 2.1996 15:40:22

0.002883905 = product of:
  0.02307124 = sum of:
    0.02307124 = weight(_text_:work in 851) [ClassicSimilarity], result of:
      0.02307124 = score(doc=851,freq=2.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.16220987 = fieldWeight in 851, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03125 = fieldNorm(doc=851)
  0.125 = coord(1/8)

Abstract

Literature review articles are essential to summarize the related work in the selected field. However, covering all related studies takes too much time and effort. This study questions how Artificial Intelligence can be used in this process. We used ChatGPT to create a literature review article to show the stage of the OpenAI ChatGPT artificial intelligence application. As the subject, the applications of Digital Twin in the health field were chosen. Abstracts of the last three years (2020, 2021 and 2022) papers were obtained from the keyword "Digital twin in healthcare" search results on Google Scholar and paraphrased by ChatGPT. Later on, we asked ChatGPT questions. The results are promising; however, the paraphrased parts had significant matches when checked with the Ithenticate tool. This article is the first attempt to show the compilation and expression of knowledge will be accelerated with the help of artificial intelligence. We are still at the beginning of such advances. The future academic publishing process will require less human effort, which in turn will allow academics to focus on their studies. In future studies, we will monitor citations to this study to evaluate the academic validity of the content produced by the ChatGPT. 1. Introduction OpenAI ChatGPT (ChatGPT, 2022) is a chatbot based on the OpenAI GPT-3 language model. It is designed to generate human-like text responses to user input in a conversational context. OpenAI ChatGPT is trained on a large dataset of human conversations and can be used to create responses to a wide range of topics and prompts. The chatbot can be used for customer service, content creation, and language translation tasks, creating replies in multiple languages. OpenAI ChatGPT is available through the OpenAI API, which allows developers to access and integrate the chatbot into their applications and systems. OpenAI ChatGPT is a variant of the GPT (Generative Pre-trained Transformer) language model developed by OpenAI. It is designed to generate human-like text, allowing it to engage in conversation with users naturally and intuitively. OpenAI ChatGPT is trained on a large dataset of human conversations, allowing it to understand and respond to a wide range of topics and contexts. It can be used in various applications, such as chatbots, customer service agents, and language translation systems. OpenAI ChatGPT is a state-of-the-art language model able to generate coherent and natural text that can be indistinguishable from text written by a human. As an artificial intelligence, ChatGPT may need help to change academic writing practices. However, it can provide information and guidance on ways to improve people's academic writing skills.

0.00164069 = product of:
  0.01312552 = sum of:
    0.01312552 = product of:
      0.02625104 = sum of:
        0.02625104 = weight(_text_:22 in 1171) [ClassicSimilarity], result of:
          0.02625104 = score(doc=1171,freq=2.0), product of:
            0.13569894 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03875087 = queryNorm
            0.19345059 = fieldWeight in 1171, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1171)
      0.5 = coord(1/2)
  0.125 = coord(1/8)

Date

23.11.2023 19:07:22