Triple
T25813873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elton and Orston railway station |
E650195
|
entity |
| Predicate | hasTimetableOperator |
P28039
|
FINISHED |
| Object | National Rail |
—
|
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: National Rail | Statement: [Elton and Orston railway station, hasTimetableOperator, National Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetableOperator Context triple: [Elton and Orston railway station, hasTimetableOperator, National Rail]
-
A.
hasTimetableProvider
chosen
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
B.
hasTimetableCode
Indicates that an entity is associated with a specific timetable code used to identify its scheduled time or service pattern.
-
C.
hasTimetableInformation
Indicates that an entity provides or is associated with detailed schedule or timetable information for another entity or service.
-
D.
hasTimetableDesignation
Indicates that an entity is assigned a specific timetable-related label or classification within a scheduling or time-planning system.
-
E.
integratedTimetableWith
Indicates that one timetable has been combined and synchronized with another to form a unified, coordinated schedule.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 22, 2026, 7:12 a.m.