Triple
T13071133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auraiya district |
E329457
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Bidhuna |
E1020450
|
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: Bidhuna | Statement: [Auraiya district, hasTown, Bidhuna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bidhuna Context triple: [Auraiya district, hasTown, Bidhuna]
-
A.
Bidhuna
chosen
Bidhuna is a town and legislative assembly constituency in the Auraiya district of Uttar Pradesh, India.
-
B.
Bhatarka
Bhatarka was an early Indian ruler who founded the Maitraka dynasty, establishing its power base in the region of present-day Gujarat.
-
C.
Baghmara
Baghmara is a town in the South Garo Hills district of Meghalaya, India, known as a gateway to nearby forests, caves, and wildlife areas.
-
D.
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.
-
E.
Varendra
Varendra is a historic region in northwestern Bengal, now largely in Bangladesh, known as an early political and cultural center of medieval Bengali kingdoms.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ee6130819095d835e7ff6a8c5b |
completed | April 10, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e26e5d6881908663444bca67b01e |
completed | May 3, 2026, 5:51 a.m. |
Created at: April 9, 2026, 9 p.m.