Triple
T32478246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyderabad–Bangalore route |
E830036
|
entity |
| Predicate | connectsRailwayDivision |
P198194
|
FINISHED |
| Object | Hyderabad division |
—
|
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: Hyderabad division | Statement: [Hyderabad–Bangalore route, connectsRailwayDivision, Hyderabad division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsRailwayDivision Context triple: [Hyderabad–Bangalore route, connectsRailwayDivision, Hyderabad division]
-
A.
railwayDivision
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.
connectsSubwayDivisions
Indicates that one entity serves as a link or junction that joins or integrates multiple subway divisions into a connected system.
-
D.
railroadSubdivision
Indicates that one railroad line or territory is a designated subdivision (operational segment) of a larger railroad network.
-
E.
railwayZoneJunction
Indicates a junction where multiple railway zones or lines intersect or connect.
- F. None of above. chosen
Provenance (4 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: May 1, 2026, 12:58 a.m.