Triple
T21713892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kökejin |
E535972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol nobility |
C35181
|
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 nobility Context triple: [Kökejin, instanceOf, Mongol nobility]
-
A.
Mongol noble
chosen
A Mongol noble is a high-ranking member of Mongol society, typically belonging to ruling or aristocratic lineages, who holds political, military, and economic power within the Mongol Empire or its successor states.
-
B.
Mongol royal house
The Mongol royal house is the ruling lineage descended from Genghis Khan that governed the Mongol Empire and its successor states, holding supreme political, military, and symbolic authority over Mongol domains.
-
C.
Manchu noble clan
A Manchu noble clan is a hereditary aristocratic lineage within Manchu society, historically holding political, military, and social privileges in the Qing dynasty’s banner system.
-
D.
Mongol imperial dynasty branch
A Mongol imperial dynasty branch is a distinct ruling line or subdivision of the broader Mongol imperial family that governed a specific territory or khanate while sharing common ancestry and political heritage with the main Mongol Empire.
-
E.
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.
- F. None of above.
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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:47 p.m.