Triple
T7626340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yiyang |
E172641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality-level division in China |
C22616
|
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 in China Context triple: [Yiyang, instanceOf, municipality-level division in China]
-
A.
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.
-
B.
county of China
A county of China is an administrative division below the prefecture level that governs a defined geographic area, including towns and townships, and manages local affairs such as public services, economic development, and social administration.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:56 p.m.