Triple
T28051241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sretensk |
E708824
|
entity |
| Predicate | borderRiverBasin |
P72732
|
FINISHED |
| Object | Amur River 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: Amur River basin | Statement: [Sretensk, borderRiverBasin, Amur River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRiverBasin Context triple: [Sretensk, borderRiverBasin, Amur River basin]
-
A.
transboundaryBasin
Indicates that a river basin or watershed extends across and is shared by the territories of two or more political or administrative jurisdictions.
-
B.
associatedRiverBasin
chosen
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
C.
countryDownstreamBasin
Indicates that one country lies within the downstream portion of a river basin relative to another country or reference point.
-
D.
resourceBasin
Indicates a relationship where a basin serves as a source or reservoir of resources for another entity or area.
-
E.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 27, 2026, 8:33 p.m.