Triple
T37814942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nederlandse Spoorwegen intercity services |
E942747
|
entity |
| Predicate | timetablePattern |
P128659
|
FINISHED |
| Object | regular interval (clockface) timetable |
—
|
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: regular interval (clockface) timetable | Statement: [Nederlandse Spoorwegen intercity services, timetablePattern, regular interval (clockface) timetable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timetablePattern Context triple: [Nederlandse Spoorwegen intercity services, timetablePattern, regular interval (clockface) timetable]
-
A.
schedulePattern
chosen
Indicates a recurring or structured timing relationship that defines when an event or action is scheduled to occur.
-
B.
shiftPattern
Indicates a recurring schedule or arrangement that defines how work or activity shifts are organized over time.
-
C.
intervalPattern
Indicates a recurring temporal relationship where events or states follow a specific, regular interval pattern between their occurrences.
-
D.
integratedTimetableWith
Indicates that one timetable has been combined and synchronized with another to form a unified, coordinated schedule.
-
E.
screenTimePattern
Indicates how an entity’s use of screens (such as duration, frequency, or timing) is distributed or structured over a given period.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.