Triple
T22198914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mouhijärvi |
E548621
|
entity |
| Predicate | hasNameInFinnish |
P23453
|
FINISHED |
| Object | Mouhijärvi |
—
|
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: Mouhijärvi | Statement: [Mouhijärvi, hasNameInFinnish, Mouhijärvi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mouhijärvi Context triple: [Mouhijärvi, hasNameInFinnish, Mouhijärvi]
-
A.
Mouhijärvi
chosen
Mouhijärvi was a former municipality in Finland that later became part of the city of Sastamala.
-
B.
Vesijärvi
Vesijärvi is a lake in the Päijät-Häme region of southern Finland, known for its recreational use and proximity to the city of Lahti.
-
C.
Reisjärvi
Reisjärvi is a small rural municipality in western Finland known for its lakes, forests, and traditional Finnish countryside character.
-
D.
Hausjärvi
Hausjärvi is a rural municipality in the Kanta-Häme region of southern Finland, known for its small villages and agricultural landscape.
-
E.
Vaalajärvi
Vaalajärvi is a small village located in the municipality of Sodankylä in Finnish Lapland.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae98808819081582a57bca6312b |
completed | April 28, 2026, 9:47 p.m. |
Created at: April 16, 2026, 8:36 p.m.