Triple
T37114114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMCT |
E919071
|
entity |
| Predicate | usedInTimetablesBy |
P21407
|
FINISHED |
| Object | Indian Railways |
—
|
NE NERFINISHED |
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: Indian Railways | Statement: [MMCT, usedInTimetablesBy, Indian Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTimetablesBy Context triple: [MMCT, usedInTimetablesBy, Indian Railways]
-
A.
isUsedInTransportTimetables
chosen
Indicates that something is employed or referenced within transport timetables or schedules.
-
B.
replacedByInTimetables
Indicates that one service or entity is superseded by another in official timetables from a certain point in time.
-
C.
usedForRailwayTimetables
Indicates that something is employed in the creation, organization, or presentation of railway timetables.
-
D.
hasTimetableDesignation
Indicates that an entity is assigned a specific timetable-related label or classification within a scheduling or time-planning system.
-
E.
integratedTimetableWith
Indicates that one timetable has been combined and synchronized with another to form a unified, coordinated schedule.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 3, 2026, 4:15 p.m.