Triple
T9301678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heald Green railway station |
E223776
|
entity |
| Predicate | hasTimetableInformation |
P87953
|
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: [Heald Green railway station, hasTimetableInformation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetableInformation Context triple: [Heald Green railway station, hasTimetableInformation, yes]
-
A.
hasTimetableProvider
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
B.
integratedTimetableWith
Indicates that one timetable has been combined and synchronized with another to form a unified, coordinated schedule.
-
C.
timeTabledBy
Indicates that an event or activity has been scheduled or placed on a timetable by a particular agent or organizing entity.
-
D.
hasCurricularStructure
Indicates that an educational program or course is organized according to a defined curricular framework or structure.
-
E.
hasSchoolHours
Indicates that an entity operates or is scheduled to function during specific school-related hours or time periods.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d1d954819098be177addafa406 |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:36 p.m.