Triple
T21243473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Delhi district |
E523541
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Bahadurgarh |
—
|
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: Bahadurgarh | Statement: [West Delhi district, borderedBy, Bahadurgarh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bahadurgarh Context triple: [West Delhi district, borderedBy, Bahadurgarh]
-
A.
Bahadurgarh
chosen
Bahadurgarh is a rapidly developing city in the Indian state of Haryana that forms part of the urban agglomeration surrounding Delhi.
-
B.
Mahendragarh
Mahendragarh is a town and district headquarters in the northern Indian state of Haryana.
-
C.
Anupgarh
Anupgarh is a town in the Ganganagar district of Rajasthan, India, known for its agricultural surroundings and proximity to the India–Pakistan border.
-
D.
Narsinghgarh
Narsinghgarh is a historic town in central India that once served as the administrative and cultural center of the former princely Narsinghgarh State.
-
E.
Ajaigarh
Ajaigarh is a historic town in Madhya Pradesh, India, known for its hilltop fort and scenic location in the Vindhya ranges.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7352507448190ba1f14cef16d69be |
completed | April 21, 2026, 8:28 a.m. |
Created at: April 16, 2026, 3:47 p.m.