Triple

T9461042
Position Surface form Disambiguated ID Type / Status
Subject Tumshuqese E228143 entity
Predicate hasAlternativeName P39 FINISHED
Object Tumshuq Saka E522301 NE FINISHED

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: Tumshuq Saka | Statement: [Tumshuqese, hasAlternativeName, Tumshuq Saka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tumshuq Saka
Context triple: [Tumshuqese, hasAlternativeName, Tumshuq Saka]
  • A. Tumshuq chosen
    Tumshuq is an ancient city in the Tarim Basin region of Xinjiang, China, historically associated with the Saka (Scythian) peoples and their Eastern Iranian languages.
  • B. Sakaar
    Sakaar is a chaotic, trash-covered planet ruled by the Grandmaster in the Marvel Cinematic Universe, known for its gladiatorial contests and bizarre cosmic detritus.
  • C. Saka
    Saka is an ancient Eastern Iranian language once spoken by the Saka people in the Tarim Basin region of Central Asia.
  • D. Tucheim
    Tucheim is a village and former municipality that is now part of the town of Genthin in the German state of Saxony-Anhalt.
  • E. Haramosh Shina
    Haramosh Shina is a regional dialect of the Shina language spoken in the Haramosh area of northern Pakistan.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca843b123881909b0e60028475d12d completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd7fcaf610819092bcd3b871665aa5 completed April 1, 2026, 8:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69d139e6cc888190a2175149c59bb138 completed April 4, 2026, 4:18 p.m.
Created at: March 30, 2026, 7:52 p.m.