Triple
T37981975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC Rail (historical) |
E947574
|
entity |
| Predicate | operatedFreightTrains |
—
|
GENERATED |
| Object | yes |
—
|
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: operatedFreightTrains Context triple: [BC Rail (historical), operatedFreightTrains, yes]
-
A.
operatedFreightServiceIn
Indicates that an entity operated a freight transportation service within or across the specified geographic area or route.
-
B.
allowsFreightTrains
Indicates that something permits or authorizes the operation or passage of freight trains.
-
C.
operatesRailNetworkOf
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
-
D.
operatedFreightInterchangeWith
Indicates that one entity operated a freight interchange service or facility jointly with another entity, enabling the transfer of freight between their respective operations.
-
E.
hasPassengerTrains
Indicates that a location, route, or rail line is served by trains that carry passengers.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.