Triple

T21194919
Position Surface form Disambiguated ID Type / Status
Subject Tumshuq E522301 entity
Predicate hasNameVariant P457 FINISHED
Object Tumshuqese 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: Tumshuqese | Statement: [Tumshuq, hasNameVariant, Tumshuqese]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tumshuqese
Context triple: [Tumshuq, hasNameVariant, Tumshuqese]
  • A. Tumshuqese chosen
    Tumshuqese is an extinct Eastern Iranian language once spoken in the region of Tumshuq in what is now Xinjiang, China.
  • B. Tumshuq
    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.
  • C. Tushemisht
    Tushemisht is a lakeside village in southeastern Albania, known for its scenic location on the shores of Lake Ohrid near the Macedonian border.
  • D. Chumashan
    Chumashan is a small family of extinct Native American languages once spoken along the southern and central coast of California.
  • E. Chamavi
    The Chamavi were an early Germanic tribe, likely part of the broader West Germanic group, known from Roman-era sources in the region of the lower Rhine.
  • 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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7333aa0fc81909b17eb6a26f389ec completed April 21, 2026, 8:20 a.m.
Created at: April 16, 2026, 3:08 p.m.