Triple
T16265380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhajjar district |
E394860
|
entity |
| Predicate | majorTown |
P316
|
FINISHED |
| Object | Bahadurgarh |
E342152
|
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: Bahadurgarh | Statement: [Jhajjar district, majorTown, Bahadurgarh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bahadurgarh Context triple: [Jhajjar district, majorTown, 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.
Anupgarh
Anupgarh is a town in the Ganganagar district of Rajasthan, India, known for its agricultural surroundings and proximity to the India–Pakistan border.
-
C.
Sardulgarh
Sardulgarh is a town in the Mansa district of Punjab, India, known for its agricultural economy and location near the Punjab–Haryana border.
-
D.
Ramgarh
Ramgarh is a town and administrative district headquarters in the Indian state of Jharkhand, known for its coal mining and industrial activities.
-
E.
Ramgarh
Ramgarh is a town in the Alwar district of Rajasthan, India, known for its historic forts, temples, and traditional Rajasthani culture.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c73944819085633e6d2a69bae9 |
completed | April 17, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00580b94c88190a3330791e505fd6a |
completed | May 10, 2026, 10:03 a.m. |
Created at: April 10, 2026, 5:05 a.m.