Triple
T11321417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulsi Lake |
E268101
|
entity |
| Predicate | outflow |
P967
|
FINISHED |
| Object | Vihar Lake |
E269505
|
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: Vihar Lake | Statement: [Tulsi Lake, outflow, Vihar Lake]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vihar Lake Context triple: [Tulsi Lake, outflow, Vihar Lake]
-
A.
Vihar Lake
chosen
Vihar Lake is an artificial freshwater reservoir in Mumbai, India, that serves as one of the city’s important sources of drinking water and lies within the Sanjay Gandhi National Park.
-
B.
Agastya Lake
Agastya Lake is a historic man-made reservoir in Badami, Karnataka, surrounded by red sandstone cliffs and ancient temples, and regarded as a sacred water body.
-
C.
Sarangan Lake
Sarangan Lake is a popular natural mountain lake and tourist destination located in the highlands of Magetan, East Java, Indonesia.
-
D.
Kunduvada Lake
Kunduvada Lake is a prominent freshwater lake and popular recreational spot located in Davangere, Karnataka, India.
-
E.
Madhukar Sagar Lake
Madhukar Sagar Lake is a prominent reservoir and scenic water body located near Mahoba in the Bundelkhand region of Uttar Pradesh, India.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9dff37081909622623e66e17ccd |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e543055b588190a417b3d50ade989a |
completed | April 19, 2026, 9:03 p.m. |
Created at: April 8, 2026, 9:32 p.m.