Triple
T17628300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azamgarh division |
E429905
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Azamgarh |
—
|
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: Azamgarh | Statement: [Azamgarh division, hasMajorTown, Azamgarh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Azamgarh Context triple: [Azamgarh division, hasMajorTown, Azamgarh]
-
A.
Azamgarh
chosen
Azamgarh is a city in the Purvanchal region of eastern Uttar Pradesh, India, known as an important cultural and educational center.
-
B.
Amroha
Amroha is a town and municipal board in Uttar Pradesh, India, known for its historical significance and cultural heritage.
-
C.
Jalaun
Jalaun is a town in the Indian state of Uttar Pradesh known for its administrative role within the surrounding Jalaun district.
-
D.
Jaunpur
Jaunpur is a historic city in the Indian state of Uttar Pradesh, known for its medieval architecture and cultural heritage.
-
E.
Ghazipur
Ghazipur is a city in the Indian state of Uttar Pradesh, known for its historical significance and as a regional hub in eastern Uttar Pradesh.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbe3a308190a818d04f1a9b15f7 |
completed | April 19, 2026, 5:53 a.m. |
Created at: April 10, 2026, 5:52 a.m.