Triple
T14407181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadowlands District |
E357229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special planning district |
C2259
|
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: special planning district Context triple: [Meadowlands District, instanceOf, special planning district]
-
A.
special-purpose district
chosen
A special-purpose district is a limited-purpose local government entity created to perform a specific public function or set of functions—such as water supply, transportation, or education—within a defined geographic area.
-
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.
land use planning area
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.
-
D.
planned commercial district
A planned commercial district is a deliberately designed area designated for concentrated business, retail, and service activities, typically guided by zoning regulations and urban planning principles to support economic activity and accessibility.
-
E.
European-planned district
A European-planned district is an urban area deliberately designed and laid out according to European planning principles, often featuring organized street grids or boulevards, designated civic and commercial zones, and architectural styles reflecting European influence.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:17 a.m.