Triple
T2612976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolar River |
E58818
|
entity |
| Predicate | Kolar DamLocation |
P31704
|
FINISHED |
| Object | near Bhopal |
—
|
LITERAL 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: near Bhopal | Statement: [Kolar River, Kolar DamLocation, near Bhopal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Kolar DamLocation Context triple: [Kolar River, Kolar DamLocation, near Bhopal]
-
A.
watercourseHasDam
Indicates that a watercourse (such as a river or stream) has a dam constructed on or across it.
-
B.
damLocation
chosen
Indicates the geographic place where a dam is situated or constructed.
-
C.
reservoirCreatedByDam
Indicates that a reservoir exists as a result of being formed or impounded by a specific dam.
-
D.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
E.
locatedInFormerLake
Indicates that an entity is situated within the area that was once occupied by a lake that no longer exists.
- F. None of above.
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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.