Triple
T3381349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VBB |
E71189
|
entity |
| Predicate | providesTimetableInformation |
P28039
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [VBB, providesTimetableInformation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesTimetableInformation Context triple: [VBB, providesTimetableInformation, true]
-
A.
usedForRailwayTimetables
Indicates that something is employed in the creation, organization, or presentation of railway timetables.
-
B.
railwayStationOnLine
Indicates that a particular railway station is located on and served by a specified railway line.
-
C.
hasTimetableProvider
chosen
Indicates that an entity is associated with a source or system that supplies its schedule or timetable information.
-
D.
isUsedInTransportTimetables
Indicates that something is employed or referenced within transport timetables or schedules.
-
E.
railwayTimeUsage
Indicates how much time is spent using or operating a railway within a given context or 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e9af608190bfb228ef99a87bb7 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.