Triple
T9461012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tumshuqese |
E228143
|
entity |
| Predicate | spokenIn |
P2266
|
FINISHED |
| Object | Tumshuq |
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 | Statement: [Tumshuqese, spokenIn, Tumshuq]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tumshuq Context triple: [Tumshuqese, spokenIn, Tumshuq]
-
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.
Tashlultum
Tashlultum was a queen of the Akkadian Empire, known primarily as the wife of the powerful ruler Naram-Sin.
-
C.
The Turim
The Turim is a foundational 14th-century Jewish legal code by Rabbi Jacob ben Asher that systematically organizes halakhic rulings into four major sections.
-
D.
Tuder
Tuder was an important ancient Umbrian settlement in central Italy, known today as the hilltop town of Todi.
-
E.
Tucheim
Tucheim is a village and former municipality that is now part of the town of Genthin in the German state of Saxony-Anhalt.
- 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_69d1229ec9448190bac9b7a38e030833 |
completed | April 4, 2026, 2:39 p.m. |
Created at: March 30, 2026, 7:52 p.m.