Triple
T32839681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunga–Bhadra confluence |
E839927
|
entity |
| Predicate | watercourseFormed |
P67263
|
FINISHED |
| Object | Tungabhadra River |
—
|
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: Tungabhadra River | Statement: [Tunga–Bhadra confluence, watercourseFormed, Tungabhadra River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseFormed Context triple: [Tunga–Bhadra confluence, watercourseFormed, Tungabhadra River]
-
A.
riverFormed
chosen
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
-
B.
watercourseHelpsForm
Indicates that a watercourse contributes to the creation, shaping, or delineation of another geographic feature or boundary.
-
C.
watercourseFor
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
D.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
-
E.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:16 a.m.