Triple
T37981974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC Rail (historical) |
E947574
|
entity |
| Predicate | operatedPassengerTrains |
P31751
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [BC Rail (historical), operatedPassengerTrains, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedPassengerTrains Context triple: [BC Rail (historical), operatedPassengerTrains, yes]
-
A.
hasPassengerTrains
Indicates that a location, route, or rail line is served by trains that carry passengers.
-
B.
operatedPassengerServices
chosen
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
C.
operatesRailNetworkOf
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
-
D.
isPassengerRail
Indicates that something functions as or is classified as a passenger rail service or system, primarily used to transport people rather than freight.
-
E.
trains
Indicates that one entity teaches, instructs, or coaches another entity to develop skills, knowledge, or abilities.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_6a0338d1074481909541e6150307e7f8 |
completed | May 12, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a03386e7da08190b533cb0e908503dd |
completed | May 12, 2026, 2:25 p.m. |
Created at: May 3, 2026, 4:20 p.m.