Triple
T8573131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayannur |
E202975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality-level division of Inner Mongolia |
C20673
|
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: municipality-level division of Inner Mongolia Context triple: [Bayannur, instanceOf, municipality-level division of Inner Mongolia]
-
A.
municipality-level division in China
A municipality-level division in China is a top-tier administrative unit directly under the central government, combining the powers of both a city and a province to govern a large urban center and its surrounding rural areas.
-
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.
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.
-
D.
province-level administrative division
chosen
A province-level administrative division is a primary subnational territorial unit within a country, governed by its own regional authorities under the framework of the national government.
-
E.
township-level division
A township-level division is a local administrative unit within a country, typically governing a small urban or rural area below the county level and responsible for basic public services and local governance.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:21 p.m.