Triple
T15425849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzbek Khan |
E369506
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Jani Beg |
E1122233
|
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: Jani Beg | Statement: [Uzbek Khan, successor, Jani Beg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jani Beg Context triple: [Uzbek Khan, successor, Jani Beg]
-
A.
Jani Beg
chosen
Jani Beg was a 14th-century khan of the Golden Horde known for expanding its power and for his role in the decline of the unified Mongol Empire.
-
B.
Safa Giray
Safa Giray was a 16th-century khan of Kazan known for his resistance to Russian expansion and his turbulent, often interrupted reign.
-
C.
Nogai
Nogai is a Turkic language spoken primarily by the Nogai people of the North Caucasus region in Russia.
-
D.
Bairam Beg
Bairam Beg, better known as Bairam Khan, was a prominent 16th-century Turkic military commander and statesman who served as regent and chief advisor to the Mughal emperor Akbar.
-
E.
Emil Ghuri
Emil Ghuri was a Palestinian Arab nationalist politician who served as a leading member and later secretary-general of the Arab Higher Committee during the British Mandate period.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec1fb288190a3625b8e4f487dd1 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1a7ed0ec8190b8086f78df965b61 |
completed | May 9, 2026, 11:29 a.m. |
Created at: April 10, 2026, 3:20 a.m.