Triple
T9141648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Central Railroad Depot (Ypsilanti) |
E219341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation landmark |
C2489
|
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: transportation landmark Context triple: [Michigan Central Railroad Depot (Ypsilanti), instanceOf, transportation landmark]
-
A.
urban landmark
An urban landmark is a prominent, easily recognizable feature within a city—such as a building, monument, or natural formation—that serves as a visual reference point and symbol of the area’s identity.
-
B.
combined civic building and transportation hub
A combined civic building and transportation hub is a multifunctional public facility that integrates government or community services with major transit infrastructure to centralize access, improve connectivity, and enhance urban efficiency.
-
C.
civil engineering landmark
A civil engineering landmark is a significant structure or project—such as a bridge, dam, tunnel, or roadway—that exemplifies notable achievement, innovation, or historical importance in the field of civil engineering.
-
D.
tourist attraction
A tourist attraction is a place, event, or feature that draws visitors due to its cultural, historical, natural, recreational, or entertainment value.
-
E.
public transportation infrastructure
chosen
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:19 p.m.