Triple
T22221304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Olkijoki |
E549214
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Oulujoki |
—
|
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: Oulujoki | Statement: [Treaty of Olkijoki, location, Oulujoki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oulujoki Context triple: [Treaty of Olkijoki, location, Oulujoki]
-
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.
Ilmajoki
Ilmajoki is a rural municipality in Southern Ostrobothnia, western Finland, known for its agricultural landscape and strong local cultural traditions.
-
C.
Kemijoki
Kemijoki is the longest river in Finland, flowing through Lapland to the Gulf of Bothnia and serving as a major source of hydroelectric power.
-
D.
Iijoki
Iijoki is a river in northern Finland that flows through the region of North Ostrobothnia into the Gulf of Bothnia.
-
E.
Kuusjoki
Kuusjoki was a former municipality in Southwest Finland that later became part of the city of Salo.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b90b1dc81908fee5fab8d5d14a2 |
completed | April 28, 2026, 9:50 p.m. |
Created at: April 16, 2026, 8:37 p.m.