Triple
T31838586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigg railway station |
E812736
|
entity |
| Predicate | hasTimetableInformationDisplays |
P192227
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Brigg railway station, hasTimetableInformationDisplays, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetableInformationDisplays Context triple: [Brigg railway station, hasTimetableInformationDisplays, yes]
-
A.
hasTimetableInformation
Indicates that an entity provides or is associated with detailed schedule or timetable information for another entity or service.
-
B.
hasTimetableDesignation
Indicates that an entity is assigned a specific timetable-related label or classification within a scheduling or time-planning system.
-
C.
hasTimetableProvider
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
D.
hasTimetableRoute
Indicates that a timetable is associated with a specific route that it schedules or defines.
-
E.
hasTimetableCode
Indicates that an entity is associated with a specific timetable code used to identify its scheduled time or service pattern.
- F. None of above. chosen
Provenance (4 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: April 30, 2026, 11:48 p.m.