Triple
T14052410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Development Committee |
E338123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district-level planning authority |
C20571
|
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: district-level planning authority Context triple: [District Development Committee, instanceOf, district-level planning authority]
-
A.
district administration
District administration is the local governing and executive authority responsible for implementing government policies, managing public services, and coordinating development activities within a defined district.
-
B.
planning district
A planning district is a defined geographic area used by governments or organizations to coordinate land use, infrastructure, and development policies.
-
C.
regional planning agency
A regional planning agency is an organization responsible for coordinating land use, transportation, infrastructure, and environmental planning across multiple jurisdictions within a defined geographic region.
-
D.
borough-level jurisdiction
A borough-level jurisdiction is an administrative division within a larger city or region that possesses localized governmental authority and responsibilities specific to that borough.
-
E.
district office
chosen
A district office is a local administrative center that manages and coordinates government or organizational services, operations, and support within a specific geographic district.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.