Triple
T27243101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jingzhou Miao and Dong Autonomous County |
E687264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ethnic autonomous county |
C43905
|
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: ethnic autonomous county Context triple: [Jingzhou Miao and Dong Autonomous County, instanceOf, ethnic autonomous county]
-
A.
autonomous prefecture
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.
-
B.
autonomous county
chosen
An autonomous county is a county-level administrative division granted a degree of self-governance, often to recognize and accommodate the political, cultural, or ethnic distinctiveness of its local population.
-
C.
autonomous region of China
An autonomous region of China is a first-level administrative division granted a degree of self-governance and cultural autonomy, typically in areas with significant ethnic minority populations.
-
D.
special autonomous region
A special autonomous region is a subnational territorial unit granted a high degree of self-governance and legislative autonomy distinct from other administrative divisions within the same country.
-
E.
autonomous district council
An autonomous district council is a local self-governing body in a specific district that exercises legislative, executive, and financial powers over designated subjects to preserve regional autonomy, culture, and development.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 10:39 a.m.