Triple
T26863378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Canyon Railway |
E676399
|
entity |
| Predicate | reopenedAsTouristRailway |
P37967
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Grand Canyon Railway, reopenedAsTouristRailway, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsTouristRailway Context triple: [Grand Canyon Railway, reopenedAsTouristRailway, 1989]
-
A.
reopenedAsPassengerLine
Indicates that a previously closed or differently used railway line has been opened again specifically for passenger services.
-
B.
isTouristRailway
Indicates that a railway is primarily operated for tourism or leisure purposes rather than as a regular public transport service.
-
C.
reopenedAsNarrowGauge
Indicates that a previously closed or different-gauge railway line was reopened with a narrow-gauge track configuration.
-
D.
openedAsHeritageRailway
chosen
Indicates that a railway line or route was reopened specifically for heritage or tourist purposes rather than for regular commercial transport service.
-
E.
openedAsRailroad
Indicates that a transportation line or route was originally inaugurated and operated as a railroad.
- 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_69f61e961a7c81908c3a7f6aebaf1242 |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:27 a.m.