Triple
T7720363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic Sea drainage basin |
E174991
|
entity |
| Predicate | hasMajorRiver |
P165
|
FINISHED |
| Object | Kemijoki |
E122150
|
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: Kemijoki | Statement: [Baltic Sea drainage basin, hasMajorRiver, Kemijoki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kemijoki Context triple: [Baltic Sea drainage basin, hasMajorRiver, Kemijoki]
-
A.
Kemijoki
chosen
Kemijoki is the longest river in Finland, flowing through Lapland to the Gulf of Bothnia and serving as a major source of hydroelectric power.
-
B.
Kuusjoki
Kuusjoki was a former municipality in Southwest Finland that later became part of the city of Salo.
-
C.
Tornionjoki
Tornionjoki is a river forming part of the border between Sweden and Finland, known for its salmon fishing and its course into the northern Gulf of Bothnia.
-
D.
Porvoonjoki
Porvoonjoki is a river in southern Finland that flows through the historic town of Porvoo before emptying into the Gulf of Finland.
-
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_69c6995d541c81909eaa646b1a8369a9 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702eedc088190be645c029dfc462a |
completed | March 27, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8b517c64881908d24e8613dc33bf4 |
completed | March 29, 2026, 5:13 a.m. |
Created at: March 27, 2026, 4:05 p.m.