Triple
T22968585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaidu |
E571117
|
entity |
| Predicate | relative |
P37
|
FINISHED |
| Object | Batu Khan |
—
|
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: Batu Khan | Statement: [Kaidu, relative, Batu Khan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Batu Khan Context triple: [Kaidu, relative, Batu Khan]
-
A.
Batu Khan
chosen
Batu Khan was a 13th-century Mongol ruler and military commander who founded the Golden Horde and led the Mongol invasions of Eastern Europe.
-
B.
Erlik Khan
Erlik Khan is a deity from Turkic and Mongolic mythology, commonly regarded as the god of death and ruler of the underworld.
-
C.
Güshi Khan
Güshi Khan was a 17th-century Oirat Mongol leader who founded the Khoshut Khanate in Tibet and played a key role in establishing the Dalai Lama’s political authority.
-
D.
Allakuli Khan
Allakuli Khan was a 19th-century khan of Khiva known for his extensive building projects and efforts to develop the city into a major Central Asian cultural and commercial center.
-
E.
Bayanchur Khan
Bayanchur Khan was an 8th-century ruler who greatly expanded and consolidated the Uyghur Khaganate, turning it into a powerful Central Asian empire.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182301f388190bb39e3d5b356dc65 |
completed | April 29, 2026, 3:59 a.m. |
Created at: April 17, 2026, 3:48 p.m.