Triple

T20194281
Position Surface form Disambiguated ID Type / Status
Subject Hylian E493041 entity
Predicate hasWritingSystem P454 FINISHED
Object Hylian script 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: Hylian script | Statement: [Hylian, hasWritingSystem, Hylian script]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hylian script
Context triple: [Hylian, hasWritingSystem, Hylian script]
  • A. Kawi script
    Kawi script is an ancient Brahmic-derived writing system historically used across Java and other parts of Southeast Asia to write Old Javanese and related languages.
  • B. Aurebesh chosen
    Aurebesh is the standardized writing system used to represent the Galactic Basic language in the Star Wars universe.
  • C. Kikakui script
    The Kikakui script is an indigenous syllabary developed in the 19th century for writing the Mende language of Sierra Leone.
  • D. Hanunóo script
    The Hanunóo script is an indigenous Brahmic-derived syllabic writing system traditionally used by the Hanunóo Mangyan people of Mindoro in the Philippines.
  • E. Tengwar
    Tengwar is a fictional script created by J.R.R. Tolkien, most famously used to write various languages of Middle-earth such as Quenya, Sindarin, and Westron.
  • 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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66ad7ed548190a893110fa2ffb144 completed April 20, 2026, 6:05 p.m.
Created at: April 11, 2026, 11:37 p.m.