Triple
T25150781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Lawn |
E630069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic residential section |
C11817
|
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 residential section Context triple: [East Lawn, instanceOf, historic residential section]
-
A.
residential historic district
chosen
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.
-
B.
historic suburb
A historic suburb is a residential area on the outskirts of a city characterized by long-established neighborhoods, preserved architecture, and cultural or historical significance.
-
C.
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.
-
D.
historic townhouse complex
A historic townhouse complex is a group of architecturally significant, attached or closely spaced residential buildings from a past era, preserved or restored to reflect their original period style and urban context.
-
E.
historic building section
A historic building section is a vertical cut-through representation of an older, culturally or architecturally significant structure that reveals its internal organization, construction methods, and spatial relationships over time.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:30 a.m.