Triple
T4872020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NH 44 |
E109106
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | Ambala |
E28747
|
NE FINISHED |
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: [NH 44, connectsCity, Ambala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ambala Context triple: [NH 44, connectsCity, 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.
Kaithal
Kaithal is a historic town in the Indian state of Haryana, known for its medieval heritage and association with the Delhi Sultanate.
-
D.
Rewari
Rewari is a historic city in the Indian state of Haryana, located near Delhi and known for its brass industry and strategic position in northern India.
-
E.
Yamunanagar
Yamunanagar is an industrial city in the Indian state of Haryana, known for its plywood, paper, and metal industries and its proximity to the Yamuna River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d9e27908190a0c4540ee2559c4b |
completed | March 20, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be67f1ca1881909a7412087fa0efab |
completed | March 21, 2026, 9:42 a.m. |
Created at: March 20, 2026, 1:27 p.m.