Triple
T38627597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riccarton Junction railway station |
E937357
|
entity |
| Predicate | nationalRailOperator |
P121930
|
FINISHED |
| Object | British Railways |
—
|
NE NERFINISHED |
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: British Railways | Statement: [Riccarton Junction railway station, nationalRailOperator, British Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalRailOperator Context triple: [Riccarton Junction railway station, nationalRailOperator, British Railways]
-
A.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
B.
hasRailTransportOperator
chosen
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
C.
isNationalRailwaySystemOf
Indicates that one entity functions as the official national railway system serving and operating within the territory of another entity.
-
D.
railwayOperatorHeadquartersIn
Indicates that the headquarters of a railway operator is located in a specified place.
-
E.
railAuthority
Indicates that an entity has official regulatory or operational control over railway systems or services.
- 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_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:32 p.m.