Triple
T17670996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mula Dam |
E440519
|
entity |
| Predicate | suppliesWaterToCity |
P4360
|
FINISHED |
| Object | Shrirampur |
—
|
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: Shrirampur | Statement: [Mula Dam, suppliesWaterToCity, Shrirampur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shrirampur Context triple: [Mula Dam, suppliesWaterToCity, Shrirampur]
-
A.
Shrirampur
chosen
Shrirampur is a prominent town in Maharashtra, India, known for its agricultural markets and role as a local commercial and educational hub.
-
B.
Vikrampur
Vikrampur was a historic urban and political center in the Bengal region, renowned as an important seat of power and culture in medieval South Asia.
-
C.
Bishrampur
Bishrampur is a municipality in southern Nepal located within Madhesh Province near the border with India.
-
D.
Rajpur
Rajpur is a town located within Nepal's Madhesh Province.
-
E.
Shyamnagar
Shyamnagar is a suburban locality in West Bengal, India, situated along the Sealdah–Ranaghat railway corridor and forming part of the greater Kolkata metropolitan 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f68a038819084828ff73bcf1fcc |
completed | April 19, 2026, 6 a.m. |
Created at: April 10, 2026, 9:59 a.m.