Triple
T9474713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amherst Street (Parkside segment) |
E228484
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic residential boulevard |
C703
|
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 boulevard Context triple: [Amherst Street (Parkside segment), instanceOf, historic residential boulevard]
-
A.
historic alley
A historic alley is a narrow passageway between buildings that preserves architectural features, materials, and spatial character from a past era, reflecting the cultural and urban history of its surroundings.
-
B.
historic road
chosen
A historic road is a transportation route of significant age and cultural, economic, or political importance, preserved or recognized for its role in shaping historical events, trade, or settlement patterns.
-
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.
historic courtyard
A historic courtyard is an open, often enclosed outdoor space surrounded by buildings or walls that reflects the architectural, cultural, and social practices of a particular past era.
-
E.
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.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:54 p.m.