Triple
T21271926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanover Street Bridge |
E524282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Baltimore landmark |
C44450
|
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: Baltimore landmark Context triple: [Hanover Street Bridge, instanceOf, Baltimore landmark]
-
A.
Boston landmark
A Boston landmark is a notable physical site, structure, or public space in Boston that holds historical, cultural, architectural, or social significance and is widely recognized as emblematic of the city.
-
B.
New York City designated landmark
A New York City designated landmark is a building, site, object, or district officially recognized and protected by the New York City Landmarks Preservation Commission for its special historical, cultural, or architectural significance.
-
C.
landmark in Washington, D.C.
A landmark in Washington, D.C. is a notable building, monument, or site within the U.S. capital that holds historical, political, cultural, or architectural significance and is often recognized as a symbol of national heritage.
-
D.
landmark in New York City
A landmark in New York City is a notable, often historically or culturally significant site, building, or structure officially recognized for its importance to the city’s heritage and identity.
-
E.
Baltimore Metro SubwayLink station
A Baltimore Metro SubwayLink station is a designated transit facility where passengers can board, alight, and transfer between Metro SubwayLink trains and other transportation modes within the Baltimore metropolitan area.
- F. None of above. chosen
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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:01 p.m.