Triple
T11887301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainy River |
E282819
|
entity |
| Predicate | majorCrossBorderRiver |
P93095
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rainy River, majorCrossBorderRiver, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCrossBorderRiver Context triple: [Rainy River, majorCrossBorderRiver, yes]
-
A.
transboundaryRiverOf
chosen
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
B.
transboundaryBasin
Indicates that a river basin or watershed extends across and is shared by the territories of two or more political or administrative jurisdictions.
-
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.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
E.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a13370819086386fecb99e4f0b |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.