Triple

T19581370
Position Surface form Disambiguated ID Type / Status
Subject Tallinna Sadam AS E489992 entity
Predicate manages P86 FINISHED
Object Paljassaare Harbour 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: Paljassaare Harbour | Statement: [Tallinna Sadam AS, manages, Paljassaare Harbour]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paljassaare Harbour
Context triple: [Tallinna Sadam AS, manages, Paljassaare Harbour]
  • A. Paljassaare Harbour chosen
    Paljassaare Harbour is a smaller cargo and industrial port area in Tallinn, Estonia, primarily handling bulk and mixed goods within the Port of Tallinn complex.
  • B. Lutakko harbour
    Lutakko harbour is a lakeside port area in Jyväskylä, Finland, known for its marina, events, and recreational waterfront.
  • C. Vuosaari Harbour
    Vuosaari Harbour is a major cargo and logistics port area in eastern Helsinki, Finland, serving as the city’s primary freight hub.
  • D. Unije harbour
    Unije harbour is the small coastal port serving the island village of Unije in Croatia’s northern Adriatic Sea, used primarily by local fishing boats and visiting yachts.
  • E. Varkaus harbour
    Varkaus harbour is a port facility in the town of Varkaus, Finland, serving as a local hub for waterborne transport and related maritime activities.
  • 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_69e640281b7c8190be44268a58df058f completed April 20, 2026, 3:03 p.m.
Created at: April 10, 2026, 1:42 p.m.