Triple
T14024295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köchü |
E337416
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Borjigin dynasty |
C33428
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: member of the Borjigin dynasty Context triple: [Köchü, instanceOf, member of the Borjigin dynasty]
-
A.
member of the Jochid dynasty
A member of the Jochid dynasty is an individual descended from Jochi, the eldest son of Genghis Khan, belonging to the ruling lineage that governed the Golden Horde and related successor states.
-
B.
member of the Tughlaq dynasty
A member of the Tughlaq dynasty is an individual belonging to the medieval Muslim ruling family that governed the Delhi Sultanate in northern India during the 14th century, known for ambitious reforms, extensive territorial control, and periods of political instability.
-
C.
Mongol ruler
A Mongol ruler is a sovereign leader of the Mongol people and their empire, wielding military, political, and often spiritual authority over vast, multiethnic territories.
-
D.
member of the Battiad dynasty
A member of the Battiad dynasty is an individual belonging to the royal lineage that ruled the ancient Greek city-state of Cyrene in North Africa, traditionally founded by Battus I and his descendants.
-
E.
member of the Ottoman dynasty
A member of the Ottoman dynasty is an individual belonging by birth or marriage to the ruling imperial family of the Ottoman Empire, historically entitled to varying degrees of political influence, privilege, and succession rights.
- F. None of above. chosen
Provenance (1 batch)
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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:19 p.m.