Triple
T17958196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haryana Urban Development Authority |
E449006
|
entity |
| Predicate | regionServed |
P82
|
FINISHED |
| Object | Mahendragarh |
E1233353
|
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: Mahendragarh | Statement: [Haryana Urban Development Authority, regionServed, Mahendragarh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mahendragarh Context triple: [Haryana Urban Development Authority, regionServed, Mahendragarh]
-
A.
Mahendragarh
chosen
Mahendragarh is a town and district headquarters in the northern Indian state of Haryana.
-
B.
Bahadurgarh
Bahadurgarh is a rapidly developing city in the Indian state of Haryana that forms part of the urban agglomeration surrounding Delhi.
-
C.
Laxmangarh
Laxmangarh is a town in the Sikar district of Rajasthan, India, known for its historic fort, havelis, and traditional Rajasthani architecture.
-
D.
Laxmangarh
Laxmangarh is a town in the Alwar district of Rajasthan, India, known for its local markets and surrounding agricultural communities.
-
E.
Anupgarh
Anupgarh is a town in the Ganganagar district of Rajasthan, India, known for its agricultural surroundings and proximity to the India–Pakistan border.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afb16bfc8190b3eb433a90f0630d |
completed | April 19, 2026, 10:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a038533279c819082861dfac6f1923e |
completed | May 12, 2026, 7:53 p.m. |
Created at: April 10, 2026, 10:21 a.m.