Triple
T28551587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riccarton Junction |
E722900
|
entity |
| Predicate | closureForGoods |
P142751
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Riccarton Junction, closureForGoods, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureForGoods Context triple: [Riccarton Junction, closureForGoods, 1969]
-
A.
closedToGoods
chosen
Indicates that an entity (such as a route, border, or facility) is not open or available for the movement, trade, or handling of goods.
-
B.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
C.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
D.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
E.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:43 a.m.