Triple
T17378126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agra railway division |
E422493
|
entity |
| Predicate | hasLine |
P35
|
FINISHED |
| Object | Delhi–Agra section |
—
|
NE NERFINISHED |
How this triple was built (3 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: Delhi–Agra section | Statement: [Agra railway division, hasLine, Delhi–Agra section]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Delhi–Agra section Context triple: [Agra railway division, hasLine, Delhi–Agra section]
-
A.
Delhi–Kanpur section
The Delhi–Kanpur section is a major railway corridor in northern India that connects the national capital Delhi with the industrial city of Kanpur, carrying heavy passenger and freight traffic.
-
B.
Agra–Mathura section
The Agra–Mathura section is a key railway line in northern India that connects the historic cities of Agra and Mathura and forms part of important regional and long-distance rail routes.
-
C.
Delhi–Mumbai line
The Delhi–Mumbai line is one of India’s busiest and most important railway corridors, connecting the national capital New Delhi with the financial hub Mumbai and passing through major cities in northern and western India.
-
D.
Delhi–Jaipur railway line
The Delhi–Jaipur railway line is a major rail corridor in northern India that connects the national capital Delhi with the capital of Rajasthan, Jaipur, serving numerous intermediate towns and cities.
-
E.
Agra–Bandikui–Jaipur line
The Agra–Bandikui–Jaipur line is a key railway route in northern India that connects the historic city of Agra with Jaipur via Bandikui, serving as an important corridor for both passenger and freight traffic.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Delhi–Agra section Target entity description: The Delhi–Agra section is a key railway corridor in northern India that connects the national capital, Delhi, with the historic city of Agra and forms part of a major passenger and tourist route.
-
A.
Delhi–Kanpur section
The Delhi–Kanpur section is a major railway corridor in northern India that connects the national capital Delhi with the industrial city of Kanpur, carrying heavy passenger and freight traffic.
-
B.
Agra–Mathura section
The Agra–Mathura section is a key railway line in northern India that connects the historic cities of Agra and Mathura and forms part of important regional and long-distance rail routes.
-
C.
Delhi–Mumbai line
The Delhi–Mumbai line is one of India’s busiest and most important railway corridors, connecting the national capital New Delhi with the financial hub Mumbai and passing through major cities in northern and western India.
-
D.
Delhi–Jaipur railway line
The Delhi–Jaipur railway line is a major rail corridor in northern India that connects the national capital Delhi with the capital of Rajasthan, Jaipur, serving numerous intermediate towns and cities.
-
E.
Agra–Bandikui–Jaipur line
The Agra–Bandikui–Jaipur line is a key railway route in northern India that connects the historic city of Agra with Jaipur via Bandikui, serving as an important corridor for both passenger and freight traffic.
- F. None of above. chosen
Provenance (2 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6ea56c8190b56d966ccf2c91f7 |
completed | April 19, 2026, 2:14 a.m. |
Created at: April 10, 2026, 5:45 a.m.