Triple
T9182536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungabhadra Right Bank Canal |
E220367
|
entity |
| Predicate | directionFromRiver |
P75396
|
FINISHED |
| Object | right bank |
—
|
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: right bank | Statement: [Tungabhadra Right Bank Canal, directionFromRiver, right bank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromRiver Context triple: [Tungabhadra Right Bank Canal, directionFromRiver, right bank]
-
A.
waterwayDirection
chosen
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
B.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
C.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
D.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
E.
positionInRiverSystem
Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc2553e548190898434aeda517407 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.