Triple

T11955822
Position Surface form Disambiguated ID Type / Status
Subject Vaajakoski–Tikkakoski waterway E284549 entity
Predicate connects P390 FINISHED
Object Vaajakoski E382654 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: Vaajakoski | Statement: [Vaajakoski–Tikkakoski waterway, connects, Vaajakoski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vaajakoski
Context triple: [Vaajakoski–Tikkakoski waterway, connects, Vaajakoski]
  • A. Vaajakoski chosen
    Vaajakoski is a district of the city of Jyväskylä in Central Finland, known for its lakeside setting and industrial history.
  • B. Valkeakoski
    Valkeakoski is a town and municipality in the Pirkanmaa region of southern Finland, known for its paper industry and lakeside setting.
  • C. Taivalkoski
    Taivalkoski is a rural municipality in Northern Ostrobothnia, Finland, known for its forests, lakes, and outdoor recreation opportunities.
  • D. Vainikkala
    Vainikkala is a small Finnish border village and railway station that serves as a key rail crossing point between Finland and Russia on the route between Helsinki and Saint Petersburg.
  • E. Tikkakoski
    Tikkakoski is a district in Jyväskylä, Finland, known for its military air base and role as a key center for the Finnish Air Force.
  • 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_69d6ab2db38c8190b1f0ed6663ef8ada completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90366fda8819083168c93abad27d4 completed April 10, 2026, 2:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f63ca1748190aad1610f22c53f7d completed May 2, 2026, 1:03 p.m.
Created at: April 8, 2026, 9:45 p.m.