Triple
T19407428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sant Kabir Nagar |
E485497
|
entity |
| Predicate | legislativeAssemblyConstituency |
P23217
|
FINISHED |
| Object | Khalilabad |
—
|
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: Khalilabad | Statement: [Sant Kabir Nagar, legislativeAssemblyConstituency, Khalilabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khalilabad Context triple: [Sant Kabir Nagar, legislativeAssemblyConstituency, Khalilabad]
-
A.
Khalilabad
chosen
Khalilabad is a town in the Indian state of Uttar Pradesh that serves as the administrative headquarters of Sant Kabir Nagar district.
-
B.
Khanabad
Khanabad is a village in the Lower Hunza region of northern Pakistan, situated in the mountainous Hunza Valley of Gilgit-Baltistan.
-
C.
Nasirabad
Nasirabad is a town and administrative area located in the Balochistan region of present-day Pakistan.
-
D.
Nasirabad
Nasirabad is a village in the Lower Hunza region of northern Pakistan, known for its mountainous terrain and proximity to the Karakoram Range.
-
E.
Nasirabad
Nasirabad is a cantonment and town in Rajasthan, India, known for its military presence and proximity to the city of Ajmer.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6257bad0c819088dd7729b6a36a94 |
completed | April 20, 2026, 1:09 p.m. |
Created at: April 10, 2026, 1:36 p.m.