Triple
T22687844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daily News Building |
E560966
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | contributing property to historic district |
C35768
|
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: contributing property to historic district Context triple: [Daily News Building, instanceOf, contributing property to historic district]
-
A.
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.
-
B.
contributing property
chosen
A contributing property is a building, structure, or site that adds to the historical integrity or significance of a designated historic district or area.
-
C.
residential historic district
A residential historic district is a geographically defined neighborhood composed primarily of homes that collectively reflect significant historical, architectural, or cultural characteristics from a particular period or periods.
-
D.
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.
-
E.
reconstructed historic district
A reconstructed historic district is an area where buildings, streetscapes, and public spaces have been rebuilt or extensively restored to replicate their historical appearance and character, often based on archival research and archaeological evidence.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:13 p.m.