Triple
T19922589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datia Municipal Council |
E478834
|
entity |
| Predicate | governs |
P760
|
FINISHED |
| Object | City of Datia |
—
|
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: City of Datia | Statement: [Datia Municipal Council, governs, City of Datia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Datia Context triple: [Datia Municipal Council, governs, City of Datia]
-
A.
City of Sagar
The City of Sagar is an urban center in the Indian state of Madhya Pradesh, known for its administrative importance, educational institutions, and cultural heritage.
-
B.
Datia town
chosen
Datia town is a historic urban center in Madhya Pradesh, India, known for its hilltop palaces, temples, and rich Bundelkhand architectural heritage.
-
C.
Fatehpur
Fatehpur is a town located within Bihar’s Gaya district in eastern India.
-
D.
Fatehpur
Fatehpur is a significant city in the Indian state of Uttar Pradesh, known as an important regional center for administration, trade, and transportation.
-
E.
Fatehpur
Fatehpur is a town in the Barabanki district of Uttar Pradesh, India, known as a local administrative and market center for surrounding rural areas.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c6919c8190a96106532580b6b6 |
completed | April 20, 2026, 4:52 p.m. |
Created at: April 10, 2026, 1:53 p.m.