Triple

T8740473
Position Surface form Disambiguated ID Type / Status
Subject Port of Helsinki E207486 entity
Predicate alsoKnownAs P39 FINISHED
Object Helsinki Port E207486 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: Helsinki Port | Statement: [Port of Helsinki, alsoKnownAs, Helsinki Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Helsinki Port
Context triple: [Port of Helsinki, alsoKnownAs, Helsinki Port]
  • A. 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.
  • B. 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.
  • 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 Helsinki chosen
    The Port of Helsinki is Finland’s busiest seaport and a major passenger and cargo hub in the Baltic Sea region.
  • E. Port of Mariehamn
    The Port of Mariehamn is the main maritime gateway of Åland’s capital, serving as a key passenger and cargo hub in the Baltic Sea.
  • 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_69ca835a03a081909d4d4cd01a18c9fb completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5d4a0cf481909c770cb39fd00fcd completed March 31, 2026, 11:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf6ef8d7f88190aea21c82da47e4a0 completed April 3, 2026, 7:40 a.m.
Created at: March 30, 2026, 6:38 p.m.