Triple
T1654832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Mongolia Autonomous Region |
E35774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous region of China |
C11263
|
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: autonomous region of China Context triple: [Inner Mongolia Autonomous Region, instanceOf, autonomous region of China]
-
A.
Special Administrative Region of China
A Special Administrative Region of China is a highly autonomous territorial unit under Chinese sovereignty that maintains its own legal, economic, and administrative systems distinct from those of mainland China.
-
B.
province of Vietnam
A province of Vietnam is a first-level administrative division governed by a provincial government under the central authority of the Vietnamese state, encompassing multiple districts, towns, and cities.
-
C.
autonomous okrug of Russia
An autonomous okrug of Russia is a type of federal subject with a degree of self-governance, typically established in areas with significant indigenous or ethnic minority populations and often administratively associated with a larger region or krai.
-
D.
province of South Korea
A province of South Korea is a primary administrative division of the country, governed by a provincial government that oversees regional affairs, services, and development across multiple cities and counties.
-
E.
province of Afghanistan
A province of Afghanistan is a primary administrative division of the country, governed by a provincial authority and comprising multiple districts, towns, and rural areas within a defined geographic region.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:29 p.m.