Triple
T9673269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roose railway station |
E234081
|
entity |
| Predicate | hasTimetablePattern |
P63521
|
FINISHED |
| Object | hourly service (typical off-peak) |
—
|
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: hourly service (typical off-peak) | Statement: [Roose railway station, hasTimetablePattern, hourly service (typical off-peak)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimetablePattern Context triple: [Roose railway station, hasTimetablePattern, hourly service (typical off-peak)]
-
A.
hasTimetableProvider
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
B.
hasTimetableInformation
Indicates that an entity provides or is associated with detailed schedule or timetable information for another entity or service.
-
C.
hasCoursePattern
Indicates that an entity follows, is associated with, or is defined by a particular course structure or pattern.
-
D.
hasPlanningPattern
Indicates that an entity follows or is associated with a particular planning pattern or structured approach to planning.
-
E.
hasScheduleType
chosen
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6c05c481909885bfdb850e7527 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.