Triple
T28078591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Basin |
E709614
|
entity |
| Predicate | sharesRiverWith |
P120213
|
FINISHED |
| Object | Lower Basin |
—
|
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: Lower Basin | Statement: [Upper Basin, sharesRiverWith, Lower Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesRiverWith Context triple: [Upper Basin, sharesRiverWith, Lower Basin]
-
A.
shareWaterway
chosen
Indicates that two or more entities are connected by and have access to the same navigable body of water, such as a river, canal, or sea route.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
betweenRiver
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
-
D.
hasRiverCounterpart
Indicates that one entity has a corresponding or analogous counterpart in the context of a river.
-
E.
isSharedWatercourseBetween
Indicates that a watercourse (such as a river, stream, or canal) is jointly used, bordered, or managed by two or more distinct entities (e.g., regions, countries, or properties).
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 27, 2026, 8:50 p.m.