Triple
T961727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central India |
E20748
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Damoh |
E120933
|
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: Damoh | Statement: [Central India, containsCity, Damoh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Damoh Context triple: [Central India, containsCity, Damoh]
-
A.
Damoh
chosen
Damoh is a city in central India that serves as the administrative headquarters of Damoh district in the state of Madhya Pradesh.
-
B.
Yamunanagar
Yamunanagar is an industrial city in the Indian state of Haryana, known for its plywood, paper, and metal industries and its proximity to the Yamuna River.
-
C.
Bhagyanagar
Bhagyanagar is an old historical name for the Indian city now known as Hyderabad.
-
D.
Gorakhpur
Gorakhpur is a prominent city in northern India known as a regional commercial, transportation, and cultural hub near the border with Nepal.
-
E.
Jamnagar
Jamnagar is a city in the Indian state of Gujarat, known for its oil refineries, brass industries, and proximity to the Gulf of Kutch.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b415ac688190bbcef455935a3116 |
completed | March 1, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acc605c85881909adc6091bb9d9f8c |
completed | March 8, 2026, 12:42 a.m. |
Created at: March 1, 2026, 7:40 p.m.