Triple
T22950211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schier |
E569992
|
entity |
| Predicate | isTransboundaryRiver |
P93095
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Schier, isTransboundaryRiver, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransboundaryRiver Context triple: [Schier, isTransboundaryRiver, true]
-
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.
transboundaryWaterInfrastructureBetween
Indicates the existence of water-related infrastructure (such as dams, canals, or pipelines) that spans or jointly serves two or more different territorial or jurisdictional areas.
-
D.
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).
-
E.
borderingWaters
Indicates that a geographic area directly touches or is adjacent to a particular body of water.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a1b334819097a4e9ea8a54209c |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.