Triple
T14741075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Möngke Khan |
E346344
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Khagan |
E69977
|
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: Khagan | Statement: [Möngke Khan, title, Khagan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khagan Context triple: [Möngke Khan, title, Khagan]
-
A.
Chanyu
Chanyu was the imperial title used by the supreme rulers of the ancient Xiongnu confederation, a powerful nomadic empire in Central Asia.
-
B.
Khagan Bayan II
Khagan Bayan II was a ruler of the Avar Khaganate in the early 7th century, known for leading the Avars during their conflicts with the Byzantine Empire and their involvement in the siege of Constantinople in 626.
-
C.
Yabghu
Yabghu was a high-ranking Turkic royal title, often held by semi-autonomous rulers or viceroys within larger steppe empires.
-
D.
Great Khan
chosen
The Great Khan was the supreme ruler of the Mongol Empire, holding ultimate authority over all Mongol khanates and conquests.
-
E.
Batu Khan
Batu Khan was a 13th-century Mongol ruler and military commander who founded the Golden Horde and led the Mongol invasions of Eastern Europe.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7345680819093e901233a064e48 |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb91fdf88190bdcc9a93289f6b7f |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:30 a.m.