Triple

T19581956
Position Surface form Disambiguated ID Type / Status
Subject Kesklinn district E490014 entity
Predicate contains P35 FINISHED
Object Port of Tallinn 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 Tallinn | Statement: [Kesklinn district, contains, Port of Tallinn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Port of Tallinn
Context triple: [Kesklinn district, contains, Port of Tallinn]
  • A. Port of Tallinn chosen
    The Port of Tallinn is Estonia’s largest and busiest seaport complex, serving as a major passenger and cargo hub on the Baltic Sea.
  • B. Port of Helsinki
    The Port of Helsinki is Finland’s busiest seaport and a major passenger and cargo hub in the Baltic Sea region.
  • C. 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.
  • D. 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.
  • E. Port of Ventspils
    The Port of Ventspils is one of Latvia’s major ice-free Baltic Sea ports, serving as a key hub for cargo transit and maritime trade in the region.
  • 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_69d8e8dd9374819098e36349b3211663 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6404e18f88190b7fec59499dd25e8 completed April 20, 2026, 3:03 p.m.
Created at: April 10, 2026, 1:42 p.m.