Triple
T35779880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMW |
E1034406
|
entity |
| Predicate | associatedWithRailwayOperator |
—
|
GENERATED |
| Object | London Overground |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRailwayOperator Context triple: [IMW, associatedWithRailwayOperator, London Overground]
-
A.
hasRailTransportOperator
chosen
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
B.
hasNearbyRailwayOperator
Indicates that a railway operator is located close to or serves the vicinity of a given entity.
-
C.
associatedLineOperator
Indicates that an entity is linked to, managed by, or otherwise connected with a specific line operator.
-
D.
hasRailOperatorNamedAfter
Indicates that a rail operator is named after the specified entity.
-
E.
hasLocalRailOperator
Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.