Triple
T24004749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore and Ohio Railroad track between Baltimore and Ellicott's Mills |
E594340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic railroad line |
C34464
|
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 railroad line Context triple: [Baltimore and Ohio Railroad track between Baltimore and Ellicott's Mills, instanceOf, historic railroad line]
-
A.
historic railroad right-of-way
chosen
A historic railroad right-of-way is a corridor of land formerly used for railroad tracks and associated infrastructure that retains cultural, transportation, or engineering significance despite no longer serving active rail operations.
-
B.
historic railroad town
A historic railroad town is a community whose growth, economy, and cultural identity were fundamentally shaped by its role as a hub or stop along early railway lines.
-
C.
historic road
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.
-
D.
historic transportation system
A historic transportation system is an organized network of vehicles, routes, and infrastructure from a past era that once facilitated the movement of people or goods and is now preserved, studied, or remembered for its cultural, technological, or historical significance.
-
E.
railroad line
A railroad line is a fixed route consisting of tracks and associated infrastructure over which trains operate to transport passengers or freight between locations.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 9:40 p.m.