Triple
T18290774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi–Ambala railway line |
E438106
|
entity |
| Predicate | endPoint |
P390
|
FINISHED |
| Object | Ambala |
—
|
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: Ambala | Statement: [Delhi–Ambala railway line, endPoint, Ambala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ambala Context triple: [Delhi–Ambala railway line, endPoint, Ambala]
-
A.
Ambala
chosen
Ambala is a historic city and important military and transportation hub in the northern Indian state of Haryana.
-
B.
Saharanpur
Saharanpur is a city in the Indian state of Uttar Pradesh known as a commercial and transportation hub, particularly for its wood carving industry and agricultural trade.
-
C.
Rohtak
Rohtak is a major city in the Indian state of Haryana, known as an educational and administrative center within the National Capital Region.
-
D.
Sirsa
Sirsa is a city in the Indian state of Haryana, known as a regional commercial and administrative center near the Rajasthan and Punjab borders.
-
E.
Kaithal
Kaithal is a historic town in the Indian state of Haryana, known for its medieval heritage and association with the Delhi Sultanate.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500fee5248190928e68ddaa4d90d7 |
completed | April 19, 2026, 4:21 p.m. |
Created at: April 10, 2026, 10:35 a.m.