Triple
T32445126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BKN |
E829121
|
entity |
| Predicate | timetableUsage |
P73352
|
FINISHED |
| Object | used in Indian Railways timetables |
—
|
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: used in Indian Railways timetables | Statement: [BKN, timetableUsage, used in Indian Railways timetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timetableUsage Context triple: [BKN, timetableUsage, used in Indian Railways timetables]
-
A.
scheduleUsage
chosen
Indicates how and when a schedule is applied or utilized in relation to associated entities or events.
-
B.
timeTabledBy
Indicates that an event or activity has been scheduled or placed on a timetable by a particular agent or organizing entity.
-
C.
gridUsage
Indicates how much and in what way an entity consumes or relies on a shared grid-based resource, such as an electrical or data grid.
-
D.
integratedTimetableWith
Indicates that one timetable has been combined and synchronized with another to form a unified, coordinated schedule.
-
E.
hasTimetableInformation
Indicates that an entity provides or is associated with detailed schedule or timetable information for another entity or service.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e5a0ec819098203f775adb5d03 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:55 a.m.