Triple
T35879769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utsjoki |
E1037474
|
entity |
| Predicate | hasInternationalRiverBorder |
P93095
|
FINISHED |
| Object | Teno River |
—
|
NE NERFINISHED |
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: Teno River | Statement: [Utsjoki, hasInternationalRiverBorder, Teno River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalRiverBorder Context triple: [Utsjoki, hasInternationalRiverBorder, Teno River]
-
A.
borderingWaters
Indicates that a geographic area directly touches or is adjacent to a particular body of water.
-
B.
transboundaryRiverOf
chosen
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
C.
bordersCountryViaWaterway
Indicates that two countries share a boundary that is defined or connected by a waterway such as a river, canal, or strait.
-
D.
borderRiverPartnerCountry
Indicates that a country shares a river border with another country.
-
E.
sharesInternationalBorderWith
Indicates that two geographic or political entities have a common boundary that is recognized as an international border.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0087de41c48190b2743a26b6d65409 |
completed | May 10, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_6a00870a8bc48190be1385579b8cc1dd |
completed | May 10, 2026, 1:24 p.m. |
Created at: May 3, 2026, 4:06 p.m.