Triple
T13661692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultanpur district |
E327012
|
entity |
| Predicate | legislativeAssemblyConstituency |
P23217
|
FINISHED |
| Object | Lambhua |
E1053958
|
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: Lambhua | Statement: [Sultanpur district, legislativeAssemblyConstituency, Lambhua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lambhua Context triple: [Sultanpur district, legislativeAssemblyConstituency, Lambhua]
-
A.
Lambhua
chosen
Lambhua is a town in the Sultanpur district of Uttar Pradesh, India, known as a local administrative and market center for surrounding rural areas.
-
B.
Bhailsa
Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
-
C.
Lhazar
Lhazar is a pastoral region in southeastern Essos inhabited by peaceful shepherding people known for their devotion to the god the Great Shepherd.
-
D.
Mohanchoti
Mohanchoti is an island located within Lake Pichola in Udaipur, Rajasthan, India.
-
E.
Singhwara
Singhwara is a town located in the Darbhanga district of the Indian state of Bihar.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc620df208190afaccf3ddd10aa60 |
completed | April 12, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f794395618819094a7f0ffcf5d3fb6 |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:52 p.m.