Triple
T32839698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunga–Bhadra confluence |
E839927
|
entity |
| Predicate | flowsIntoViaFormedRiver |
P67263
|
FINISHED |
| Object | Bay of Bengal |
—
|
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: Bay of Bengal | Statement: [Tunga–Bhadra confluence, flowsIntoViaFormedRiver, Bay of Bengal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsIntoViaFormedRiver Context triple: [Tunga–Bhadra confluence, flowsIntoViaFormedRiver, Bay of Bengal]
-
A.
riverFormed
chosen
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
-
B.
flowsIntoViaMainRiver
Indicates that one water body ultimately flows into another through the course of a primary or main river channel.
-
C.
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.
-
D.
flowsToBodyOfWater
Indicates that a fluid or water source moves or is directed into a specified body of water.
-
E.
riverbedDivertedTo
Indicates that the natural course of a riverbed has been redirected or channeled toward another location or pathway.
- 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_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.