Triple
T22925106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elkridge Landing historic area |
E569280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | preserved historic area |
C24185
|
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: preserved historic area Context triple: [Elkridge Landing historic area, instanceOf, preserved historic area]
-
A.
historical district
chosen
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.
-
B.
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.
-
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.
Conservation area
A conservation area is a designated geographic region managed to protect and preserve its natural, cultural, or historical resources and biodiversity from degradation or unsustainable use.
-
E.
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.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:43 p.m.