Triple
T8031989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinggan League |
E187006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prefecture-level division |
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: prefecture-level division Context triple: [Hinggan League, instanceOf, prefecture-level division]
-
A.
prefecture
A prefecture is an administrative division or jurisdiction within a country, typically governed by a prefect and possessing certain local governmental powers.
-
B.
province-level administrative division
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.
-
C.
prefecture of department
A prefecture of department is an administrative division within a country, typically overseen by a prefect and serving as the central authority for local governance, public services, and implementation of national policies in its jurisdiction.
-
D.
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.
-
E.
provincial-level city
A provincial-level city is an urban administrative division that holds the same rank as a province or is directly governed at the provincial level, typically encompassing both a central city and surrounding rural or suburban areas.
- 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.