Triple
T2866379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Boulevard Historic District |
E63448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural district |
C11818
|
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: architectural district Context triple: [Jackson Boulevard Historic District, instanceOf, architectural district]
-
A.
architectural ensemble
An architectural ensemble is a coherent group of buildings and spaces designed or evolved together to form a unified, contextually integrated spatial and aesthetic whole.
-
B.
historic district feature
A historic district feature is a physical element, structure, or landscape component within a designated historic area that contributes to its historical, architectural, or cultural significance.
-
C.
National Historic Landmark district
A National Historic Landmark district is a geographically defined area recognized by the U.S. federal government for containing a concentration of buildings, structures, sites, or landscapes that collectively possess exceptional value in illustrating or interpreting the heritage of the United States.
-
D.
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.
-
E.
historic district contributing property
A historic district contributing property is a building, structure, site, or object within a designated historic district that adds to the district’s historical, architectural, or cultural significance.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:02 p.m.