Triple
T14602781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Tolui |
E342745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol imperial dynasty branch |
C35130
|
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: Mongol imperial dynasty branch Context triple: [House of Tolui, instanceOf, Mongol imperial dynasty branch]
-
A.
Borjigin dynasty member
A Borjigin dynasty member is an individual belonging to the royal clan descended from Genghis Khan that ruled and influenced Mongol and related polities across Eurasia.
-
B.
member of the Borjigin dynasty
A member of the Borjigin dynasty is an individual belonging to the royal lineage founded by Genghis Khan, historically ruling the Mongol Empire and its successor states.
-
C.
Mongol successor state
A Mongol successor state is a political entity that emerged from the fragmentation of the Mongol Empire, inheriting its territories, institutions, and ruling elites while developing distinct regional identities and governance structures.
-
D.
Mongol imperial council
The Mongol imperial council was a high-level advisory and decision-making body of Mongol rulers, composed of princes, generals, and nobles who deliberated on matters of war, governance, succession, and law.
-
E.
Rurikid dynasty branch
A Rurikid dynasty branch is a lineage subgroup descending from the medieval Rurikid ruling family, typically associated with a specific territory, princely title, and period of political influence in Eastern Europe.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:25 a.m.