Triple

T5226793
Position Surface form Disambiguated ID Type / Status
Subject Pirita E118010 entity
Predicate contains P35 FINISHED
Object Pirita Marina E118010 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: Pirita Marina | Statement: [Pirita, contains, Pirita Marina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pirita Marina
Context triple: [Pirita, contains, Pirita Marina]
  • A. Paljassaare Harbour
    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. Port of Kymi
    Port of Kymi is a coastal harbor facility in the town of Kymi in Greece, serving local maritime transport and regional shipping activities.
  • C. Lutakko harbour
    Lutakko harbour is a lakeside port area in Jyväskylä, Finland, known for its marina, events, and recreational waterfront.
  • D. 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.
  • E. Pirita chosen
    Pirita is a coastal district of Tallinn, Estonia, known for its beaches, marina, and extensive green areas.
  • 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_69bd4466fb8c819083b806a79414d7e4 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7addbdb88190baf9f47fc4cbb7fc completed March 20, 2026, 4:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69beeffea8f481909c86c932781c4e2a completed March 21, 2026, 7:22 p.m.
Created at: March 20, 2026, 1:48 p.m.