Triple

T9064265
Position Surface form Disambiguated ID Type / Status
Subject Egentliga Finland E217202 entity
Predicate hasMajorPort P942 FINISHED
Object Port of Turku E413226 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: Port of Turku | Statement: [Egentliga Finland, hasMajorPort, Port of Turku]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Port of Turku
Context triple: [Egentliga Finland, hasMajorPort, Port of Turku]
  • A. Port of Turku chosen
    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.
  • B. 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.
  • 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 Helsinki
    The Port of Helsinki is Finland’s busiest seaport and a major passenger and cargo hub in the Baltic Sea region.
  • E. Port of Oulu
    The Port of Oulu is a key Finnish seaport on the Gulf of Bothnia that serves as an important hub for regional cargo traffic and industry.
  • 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_69ca83d5a7f48190b16c1e59bd43ede0 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc94bb26588190b7d6f2d70819e86f completed April 1, 2026, 3:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69d01798a79081909885a8e61bf04dc3 completed April 3, 2026, 7:40 p.m.
Created at: March 30, 2026, 7:11 p.m.