Triple
T36967871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diss railway station |
E914476
|
entity |
| Predicate | hasTimetableGroup |
P28039
|
FINISHED |
| Object | Anglia |
—
|
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: Anglia | Statement: [Diss railway station, hasTimetableGroup, Anglia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetableGroup Context triple: [Diss railway station, hasTimetableGroup, Anglia]
-
A.
hasTimetableCode
Indicates that an entity is associated with a specific timetable code used to identify its scheduled time or service pattern.
-
B.
hasTimetableProvider
chosen
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
C.
hasTimetableStructure
Indicates that something follows, defines, or is associated with a specific timetable or scheduling structure.
-
D.
hasTimetableInformation
Indicates that an entity provides or is associated with detailed schedule or timetable information for another entity or service.
-
E.
hasTimetableRoute
Indicates that a timetable is associated with a specific route that it schedules or defines.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 3, 2026, 4:14 p.m.