Triple
T17620418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissioners' Plan of 1811 |
E429694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic planning blueprint |
C1381
|
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: historic planning blueprint Context triple: [Commissioners' Plan of 1811, instanceOf, historic planning blueprint]
-
A.
landmark planning blueprint
A landmark planning blueprint is a strategic, visual, and documented plan that outlines the design, placement, significance, and long-term development of key landmarks within a geographic or urban context.
-
B.
historic district plan
A historic district plan is a comprehensive guiding document that outlines policies, design standards, and preservation strategies to protect and enhance the cultural, architectural, and historical character of a designated area.
-
C.
historic urban layout
chosen
A historic urban layout is the enduring spatial arrangement of streets, plots, public spaces, and building patterns that reflects the social, economic, and cultural organization of a city in a past period.
-
D.
governing blueprint
A governing blueprint is a high-level, authoritative plan or framework that defines the structure, rules, and guiding principles by which a system, organization, or society is directed and managed.
-
E.
heritage site development plan
A heritage site development plan is a strategic framework that guides the conservation, use, and enhancement of a heritage site while balancing cultural significance, visitor experience, community needs, and sustainable 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.