Triple
T5805068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oulu |
E128725
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Oulujoki River |
E160638
|
NE 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: Oulujoki River | Statement: [Oulu, locatedOn, Oulujoki River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oulujoki River Context triple: [Oulu, locatedOn, Oulujoki River]
-
A.
Oulujoki
chosen
Oulujoki is a river in northern Finland that flows from Lake Oulujärvi to the city of Oulu and into the Gulf of Bothnia.
-
B.
Lapuanjoki River
The Lapuanjoki River is a river in western Finland that flows through the South Ostrobothnia region before emptying into the Gulf of Bothnia.
-
C.
Ounasjoki
Ounasjoki is a major river in Finnish Lapland known for its largely unregulated, natural course and importance to the region’s ecosystems and traditional livelihoods.
-
D.
Nokianvirta River
The Nokianvirta River is a waterway in southwestern Finland that flows through the town of Nokia and has historically influenced the region’s settlement and industry.
-
E.
Tourujoki
Tourujoki is a small river in central Finland that flows through the city of Jyväskylä and into Lake Päijänne.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1461a48190be2042dd3823d02e |
completed | March 22, 2026, 5:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c09836d00881908c210b2932d67519 |
completed | March 23, 2026, 1:32 a.m. |
Created at: March 22, 2026, 3:52 p.m.