Triple
T20550855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers Pass |
E504592
|
entity |
| Predicate | railwayCompletedThroughPass |
P51374
|
FINISHED |
| Object | 1885 |
—
|
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: 1885 | Statement: [Rogers Pass, railwayCompletedThroughPass, 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayCompletedThroughPass Context triple: [Rogers Pass, railwayCompletedThroughPass, 1885]
-
A.
completedAsThroughRoute
Indicates that an action or journey was carried out by following a designated through route from start to finish.
-
B.
railServiceEnded
Indicates that a previously operating rail service has been discontinued or terminated.
-
C.
routeCompleted
chosen
Indicates that a specified route has been fully traversed or finished by the relevant entity or process.
-
D.
hasThroughPassengersWith
Indicates that two transportation segments, services, or locations are connected by passengers who travel through them without starting or ending their journey there.
-
E.
railwayAccess
Indicates that an entity has direct access to, connection with, or service by a railway line or station.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5d8b55081909c3e3e972aff846d |
completed | April 20, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.