Triple
T11422308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi NCR |
E270654
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Sonipat |
E340091
|
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: Sonipat | Statement: [Delhi NCR, hasMajorCity, Sonipat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sonipat Context triple: [Delhi NCR, hasMajorCity, Sonipat]
-
A.
Sonipat
chosen
Sonipat is a rapidly developing city in the northern Indian state of Haryana that forms part of the extended urban and economic area around Delhi.
-
B.
Bhind
Bhind is a city in the northern part of the Indian state of Madhya Pradesh, known as an administrative and commercial center of the region.
-
C.
Etawah
Etawah is a city in the Indian state of Uttar Pradesh, known for its location near the Chambal ravines and as an important regional administrative and transportation center.
-
D.
Anupgarh
Anupgarh is a town in the Ganganagar district of Rajasthan, India, known for its agricultural surroundings and proximity to the India–Pakistan border.
-
E.
Palwal
Palwal is a city in the Indian state of Haryana that forms part of the extended urban area surrounding Delhi.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b357e88190ace56d36a945688f |
completed | April 9, 2026, 7:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5e8e371948190a37609aad75a4bfd |
completed | April 20, 2026, 8:50 a.m. |
Created at: April 8, 2026, 9:34 p.m.