Triple
T23532414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Yokohama Electric Railway (portion of lines) |
E576605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former interurban railway infrastructure |
C17649
|
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: former interurban railway infrastructure Context triple: [Tokyo Yokohama Electric Railway (portion of lines), instanceOf, former interurban railway infrastructure]
-
A.
former railway facility
A former railway facility is a decommissioned or repurposed site that once served operational functions for rail transport, such as stations, depots, yards, or maintenance buildings.
-
B.
interurban railroad
chosen
An interurban railroad is an electric railway system that provides passenger and sometimes freight service between cities and towns, typically operating on dedicated tracks or street-running routes over medium distances.
-
C.
former railway station
A former railway station is a decommissioned train facility that once served passengers or freight but is no longer in active railway use.
-
D.
rail transportation infrastructure
Rail transportation infrastructure encompasses the physical and organizational systems—such as tracks, stations, signaling, power supply, and related facilities—required to support the safe and efficient movement of trains and rail-based services.
-
E.
historic railroad right-of-way
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.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:10 p.m.