Triple

T22649589
Position Surface form Disambiguated ID Type / Status
Subject Expo Go E559057 entity
Predicate writtenIn P12727 FINISHED
Object JavaScript NE NERFINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: JavaScript | Statement: [Expo Go, writtenIn, JavaScript]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: JavaScript
Context triple: [Expo Go, writtenIn, JavaScript]
  • A. JavaScript chosen
    JavaScript is a high-level, dynamic programming language primarily used to create interactive and dynamic content on web pages.
  • B. JS
    JS is the youth wing of the Dutch Labour Party (PvdA), organizing and representing young social democrats in the Netherlands.
  • C. JS
    JS is the commonly used abbreviation for the United States military’s Joint Staff, which assists the Chairman of the Joint Chiefs of Staff in strategic planning and coordination among the armed services.
  • D. JS
    JS is the IATA airline designator assigned to Air Koryo, the state-owned flag carrier of North Korea.
  • E. JS
    JS is the commonly used abbreviation for the Juventud Socialista de Chile, the youth wing of Chile's Socialist Party.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69e245489dd88190b1f674acf61c8769 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1703a84b081909a683f8c850dcbf9 completed April 29, 2026, 2:43 a.m.
Created at: April 17, 2026, 3:05 p.m.