Triple
T8031991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinggan League |
E187006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | league of Inner Mongolia |
C11187
|
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: league of Inner Mongolia Context triple: [Hinggan League, instanceOf, league of Inner Mongolia]
-
A.
province of Mongolia
A province of Mongolia is a primary administrative division of the country, governed by a local authority under national law and encompassing multiple districts, settlements, and geographic regions.
-
B.
district of Ulaanbaatar
A district of Ulaanbaatar is an administrative subdivision of Mongolia’s capital city, responsible for local governance, public services, and community development within its designated urban area.
-
C.
Mongolic people
Mongolic people are an ethno-linguistic group originating from the Mongolian Plateau, historically associated with nomadic pastoralism and the Mongol Empire, and today encompassing various Mongol-speaking populations across Mongolia, China, Russia, and neighboring regions.
-
D.
nomadic empire
A nomadic empire is a large, often militaristic polity built and ruled by mobile pastoral or steppe peoples who control vast territories and diverse sedentary populations without fully settling them.
-
E.
autonomous prefecture
chosen
An autonomous prefecture is an administrative division granted a degree of self-governance, typically to recognize and accommodate the political, cultural, and linguistic rights of a specific ethnic or regional minority group within a larger state.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:22 p.m.