Triple
T26863377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Canyon Railway |
E676399
|
entity |
| Predicate | passengerServiceSuspended |
P10433
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Grand Canyon Railway, passengerServiceSuspended, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerServiceSuspended Context triple: [Grand Canyon Railway, passengerServiceSuspended, 1968]
-
A.
offersScheduledPassengerService
Indicates that an entity provides planned, regular passenger transportation services according to a published schedule.
-
B.
openedAsPassengerService
Indicates that a transportation facility or route began operating specifically for carrying passengers.
-
C.
closedForPassengers
chosen
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
D.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
E.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 5:27 a.m.