Triple
T13592021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DXN |
E324713
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Jewar |
E751727
|
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: Jewar | Statement: [DXN, locatedIn, Jewar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jewar Context triple: [DXN, locatedIn, Jewar]
-
A.
Jewar
chosen
Jewar is a town in Uttar Pradesh, India, known for its rapidly developing infrastructure and the upcoming Noida International (Jewar) Airport project.
-
B.
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.
-
C.
Sonipat
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.
-
D.
Shivpuri
Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
-
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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb056ce088190a6feb4266633d18b |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78ae1d1b08190ad07b159ac3eba4b |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:49 p.m.