Triple

T18739008
Position Surface form Disambiguated ID Type / Status
Subject Kemi-Tornio E458240 entity
Predicate hasPort P35 FINISHED
Object Port of Tornio 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: Port of Tornio | Statement: [Kemi-Tornio, hasPort, Port of Tornio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Port of Tornio
Context triple: [Kemi-Tornio, hasPort, Port of Tornio]
  • A. Port of Tornio chosen
    The Port of Tornio is a Finnish seaport on the northern Gulf of Bothnia that serves as an important industrial and cargo hub near the Swedish border.
  • B. Port of Kemi
    The Port of Kemi is a Finnish seaport on the northern Gulf of Bothnia that serves as an important hub for regional industry and cargo traffic in Lapland.
  • C. Port of Pori
    The Port of Pori is a significant Finnish seaport on the west coast that serves as an important hub for the country’s maritime trade and cargo traffic.
  • D. Port of Kotka
    The Port of Kotka is a major Finnish seaport on the Gulf of Finland that serves as an important hub for international cargo traffic and logistics.
  • E. Port of Turku
    The Port of Turku is a major Finnish seaport on the Baltic Sea that serves as an important hub for passenger ferries and cargo traffic between Finland and other Northern European countries.
  • 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_69d8d394dc308190b6725073f5db324c completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5768ca990819098102f8522ce401f completed April 20, 2026, 12:42 a.m.
Created at: April 10, 2026, 11:51 a.m.