Triple
T21200483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ounasjoki |
E522440
|
entity |
| Predicate | hasFinnishName |
P1435
|
FINISHED |
| Object | Ounasjoki |
E522440
|
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: Ounasjoki | Statement: [Ounasjoki, hasFinnishName, Ounasjoki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ounasjoki Context triple: [Ounasjoki, hasFinnishName, Ounasjoki]
-
A.
Ounasjoki
chosen
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.
-
B.
Lumijoki
Lumijoki is a small rural municipality in northern Finland known for its flat landscapes, agriculture, and proximity to the Gulf of Bothnia.
-
C.
Kuusjoki
Kuusjoki was a former municipality in Southwest Finland that later became part of the city of Salo.
-
D.
Sanginjoki
Sanginjoki is a river in northern Finland that serves as one of the tributaries feeding into the larger Oulujoki watercourse.
-
E.
Oulujoki
Oulujoki is a river in northern Finland that flows from Lake Oulujärvi to the city of Oulu and into the Gulf of Bothnia.
- 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73430c5a08190aeb6a62eec0f43a3 |
completed | April 21, 2026, 8:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09cfda4060819094b0c8f48d2c5758 |
completed | May 17, 2026, 2:25 p.m. |
Created at: April 16, 2026, 3:18 p.m.