Triple
T22120260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dindori (Lok Sabha constituency) |
E546645
|
entity |
| Predicate | containsAssemblySegments |
P63908
|
FINISHED |
| Object | Nandgaon |
—
|
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: Nandgaon | Statement: [Dindori (Lok Sabha constituency), containsAssemblySegments, Nandgaon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nandgaon Context triple: [Dindori (Lok Sabha constituency), containsAssemblySegments, Nandgaon]
-
A.
Nandgaon
Nandgaon is a historic town in the Braj region of India, revered in Hindu tradition as the childhood home of Lord Krishna and an important pilgrimage site.
-
B.
Nandgaon
chosen
Nandgaon is a town in the Nashik district of Maharashtra, India, known for its agricultural surroundings and rail connectivity.
-
C.
Ambegaon
Ambegaon is a town in the Pune district of Maharashtra, India, known for its semi-rural setting and proximity to the Western Ghats.
-
D.
Nandod
Nandod is the former name of the town now known as Rajpipla in the Indian state of Gujarat.
-
E.
Nandgaon Khandeshwar
Nandgaon Khandeshwar is a town in the Indian state of Maharashtra, known for its local governance role and its location within the Vidarbha region.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12951fcd48190841319cd879c15cb |
completed | April 28, 2026, 9:40 p.m. |
Created at: April 16, 2026, 8:31 p.m.