Triple

T18739007
Position Surface form Disambiguated ID Type / Status
Subject Kemi-Tornio E458240 entity
Predicate hasPort P35 FINISHED
Object Port of Kemi 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 Kemi | Statement: [Kemi-Tornio, hasPort, Port of Kemi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Port of Kemi
Context triple: [Kemi-Tornio, hasPort, Port of Kemi]
  • A. Port of Kemi chosen
    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.
  • B. Port of Kokkola
    The Port of Kokkola is a major Finnish seaport on the Gulf of Bothnia that serves as an important hub for bulk cargo, industry, and international trade.
  • C. 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.
  • D. 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.
  • E. Port of Kuopio
    The Port of Kuopio is an inland harbor in Kuopio, Finland, serving as a key passenger and cargo hub on Lake Kallavesi and the Saimaa lake system.
  • 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.