Triple
T15104258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Surji-Anjangaon |
E360746
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Anjangaon |
E784043
|
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: Anjangaon | Statement: [Treaty of Surji-Anjangaon, location, Anjangaon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anjangaon Context triple: [Treaty of Surji-Anjangaon, location, Anjangaon]
-
A.
Ambegaon
Ambegaon is a town in the Pune district of Maharashtra, India, known for its semi-rural setting and proximity to the Western Ghats.
-
B.
Asangaon
Asangaon is a town in Maharashtra, India, served as a suburban railway stop on Mumbai’s Central Line and known as a growing residential and industrial area on the city’s outskirts.
-
C.
Anjangaon Surji
chosen
Anjangaon Surji is a town in the Amravati district of Maharashtra, India, known primarily as a local commercial and agricultural center.
-
D.
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.
-
E.
Nandgaon
Nandgaon is a town in the Nashik district of Maharashtra, India, known for its agricultural surroundings and rail connectivity.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00551521c8190b48d1a074bb4bdfc |
completed | April 15, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae274f6881908931569efc09996e |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:05 a.m.