Triple
T24022297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onggirat territory |
E594856
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol-era territory |
C12380
|
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-era territory Context triple: [Onggirat territory, instanceOf, Mongol-era territory]
-
A.
institution of the Mongol Empire
An institution of the Mongol Empire is an organized structure or system—such as administrative offices, legal codes, military units, or religious frameworks—established by Mongol authorities to govern, manage, and integrate their vast, multiethnic empire.
-
B.
Mongol successor state
chosen
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.
-
C.
Yuan dynasty era
The Yuan dynasty era refers to the period (1271–1368) when the Mongol-led Yuan dynasty ruled China, marked by vast Eurasian integration, cultural exchange, and significant developments in administration, trade, and the arts.
-
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.
Iron Age territory
An Iron Age territory is a geographically defined area controlled by a community or polity during the Iron Age, characterized by shared cultural practices, political organization, and economic activities.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:51 p.m.