Triple
T14003542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokhtamysh |
E336889
|
entity |
| Predicate | enemy |
P4567
|
FINISHED |
| Object | Timur |
E66140
|
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: Timur | Statement: [Tokhtamysh, enemy, Timur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Timur Context triple: [Tokhtamysh, enemy, Timur]
-
A.
Timur
Timur is a deposed Tatar king and the blind, exiled father of Prince Calaf in Giacomo Puccini’s opera "Turandot."
-
B.
Timur
chosen
Timur, also known as Tamerlane, was a 14th-century Turco-Mongol conqueror who founded the Timurid Empire in Central Asia and became one of history’s most formidable military leaders.
-
C.
Tughlugh Timur
Tughlugh Timur was a 14th-century khan who reunified Moghulistan, promoted Islam in the region, and laid the foundations for later Timurid and Central Asian polities.
-
D.
Timuri
Timuri are a small ethnic group in Afghanistan and Iran, traditionally semi-nomadic and known for their distinct dialect and cultural practices within the broader Aimaq community.
-
E.
Temür Khan
Temür Khan was a Yuan dynasty emperor and grandson of Kublai Khan who ruled China and the Mongol Empire in the late 13th and early 14th centuries.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed1d2548190bb46d6b7cba4ffde |
completed | April 14, 2026, 12:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf06a3e208190a24e6cd9cb97e99c |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 9, 2026, 10:19 p.m.