Triple
T6939579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oulujoki |
E160638
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object |
Kiehimäjoki
Kiehimäjoki is a river in northern Finland that flows through the Kainuu region and serves as one of the headwaters of the Oulujoki river system.
|
E632348
|
NE FINISHED |
How this triple was built (4 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: Kiehimäjoki | Statement: [Oulujoki, hasTributary, Kiehimäjoki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kiehimäjoki Context triple: [Oulujoki, hasTributary, Kiehimäjoki]
-
A.
Kokemäenjoki
Kokemäenjoki is a major river in southwestern Finland that flows from the Pirkanmaa region to the Gulf of Bothnia, passing through several towns and historically important industrial areas.
-
B.
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.
-
C.
Kuusjoki
Kuusjoki was a former municipality in Southwest Finland that later became part of the city of Salo.
-
D.
Tenniöjoki
Tenniöjoki is a river in northern Finland that serves as a significant tributary within the Kemijoki river system.
-
E.
Kutujoki
Kutujoki is a river in Finland that serves as one of the tributaries feeding into the larger Oulujoki river system.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Kiehimäjoki Triple: [Oulujoki, hasTributary, Kiehimäjoki]
Generated description
Kiehimäjoki is a river in northern Finland that flows through the Kainuu region and serves as one of the headwaters of the Oulujoki river system.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Kiehimäjoki Target entity description: Kiehimäjoki is a river in northern Finland that flows through the Kainuu region and serves as one of the headwaters of the Oulujoki river system.
-
A.
Kokemäenjoki
Kokemäenjoki is a major river in southwestern Finland that flows from the Pirkanmaa region to the Gulf of Bothnia, passing through several towns and historically important industrial areas.
-
B.
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.
-
C.
Kuusjoki
Kuusjoki was a former municipality in Southwest Finland that later became part of the city of Salo.
-
D.
Tenniöjoki
Tenniöjoki is a river in northern Finland that serves as a significant tributary within the Kemijoki river system.
-
E.
Kutujoki
chosen
Kutujoki is a river in Finland that serves as one of the tributaries feeding into the larger Oulujoki river system.
- F. None of above.
Provenance (5 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da641ce08190a133c9ba4977755d |
completed | March 27, 2026, 7:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c769fa17748190a1ca72ca86cce827 |
completed | March 28, 2026, 5:41 a.m. |
| NEDg | Description generation | batch_69c76c55c7f48190b76a19dd6177f0a6 |
completed | March 28, 2026, 5:51 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c76cc177f481908f19d1a1eb88301a |
completed | March 28, 2026, 5:53 a.m. |
Created at: March 27, 2026, 2:28 p.m.