Triple
T38627598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riccarton Junction railway station |
E937357
|
entity |
| Predicate | closedToPassengersOn |
P10433
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Riccarton Junction railway station, closedToPassengersOn, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToPassengersOn Context triple: [Riccarton Junction railway station, closedToPassengersOn, 1963]
-
A.
closedForPassengers
chosen
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
B.
closedForRailServiceBy
Indicates that something has been closed or shut down due to rail service activities carried out by a specified agent or authority.
-
C.
closedOffFrom
Indicates that one entity is isolated, blocked, or prevented from accessing, interacting with, or being influenced by another entity.
-
D.
closedDuring
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
E.
closedForNavigation
Indicates that a route, passage, or waterway is temporarily or permanently unavailable for travel or transit.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4:32 p.m.