Triple
T26647620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanded railway division |
E668961
|
entity |
| Predicate | isRailwayDivisionOf |
P1921
|
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: [Nanded railway division, isRailwayDivisionOf, Indian Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRailwayDivisionOf Context triple: [Nanded railway division, isRailwayDivisionOf, Indian Railways]
-
A.
railwayDivision
chosen
Indicates that one administrative railway division is responsible for, manages, or encompasses another railway unit, line, or area within a rail network.
-
B.
railwayDivisionHeadquartersOf
Indicates that one location serves as the administrative headquarters for a specified railway division.
-
C.
railroadSubdivision
Indicates that one railroad line or territory is a designated subdivision (operational segment) of a larger railroad network.
-
D.
isRailwayStationInNetwork
Indicates that a railway station belongs to, and is served as part of, a particular railway network.
-
E.
servedByRailBranch
Indicates that a location or facility is connected to and provided service by a specific railway branch line.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:31 a.m.