Triple
T23865035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Dallas Landmark |
E592554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal historic designation |
C826
|
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: municipal historic designation Context triple: [City of Dallas Landmark, instanceOf, municipal historic designation]
-
A.
historic designation
chosen
A historic designation is an official recognition granted to a place, structure, or object for its significant historical, architectural, cultural, or archaeological value, often providing it with legal protections and conservation guidelines.
-
B.
cultural heritage designation
A cultural heritage designation is an official recognition granted by an authority to protect and preserve places, objects, or practices of significant historical, cultural, or artistic value.
-
C.
historic municipal building
A historic municipal building is a long-standing public structure, such as a city hall or courthouse, that has served governmental or civic functions and holds architectural, cultural, or historical significance for a community.
-
D.
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.
-
E.
historical district
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:13 p.m.