Triple
T20238108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ain River basin |
E498206
|
entity |
| Predicate | mouthBasinFor |
P139358
|
FINISHED |
| Object | confluence of Ain River with Rhône River |
—
|
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: confluence of Ain River with Rhône River | Statement: [Ain River basin, mouthBasinFor, confluence of Ain River with Rhône River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthBasinFor Context triple: [Ain River basin, mouthBasinFor, confluence of Ain River with Rhône River]
-
A.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
-
B.
basinServed
Indicates that a particular basin is supplied, drained, or otherwise functionally supported by another entity (such as a river, watershed, or infrastructure system).
-
C.
formsBasinWith
Indicates that one geographic feature combines with another to create or define a shared basin or catchment area.
-
D.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
E.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
- F. None of above. chosen
Provenance (4 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716b4c148190bf663b8a747fbfa5 |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:40 p.m.