Triple
T13289347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barren River Area Development District |
E316526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | area development district |
C13499
|
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: area development district Context triple: [Barren River Area Development District, instanceOf, area development district]
-
A.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
B.
urban administrative area
An urban administrative area is a geographically defined part of a city or town governed by specific local authorities responsible for public services, regulation, and planning within its boundaries.
-
C.
infrastructure development zone
An infrastructure development zone is a designated geographic area prioritized for the planning, investment, and construction of essential public facilities and services—such as transportation, utilities, and communications—to support economic growth and urban or regional development.
-
D.
autonomous area
An autonomous area is a geographically defined region that possesses a degree of self-governance and decision-making authority independent from the central governing body.
-
E.
land use planning area
chosen
A land use planning area is a defined geographic region designated for coordinated management and regulation of land uses to achieve specific environmental, social, and economic development objectives.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:27 p.m.