Triple

T20382068
Position Surface form Disambiguated ID Type / Status
Subject Lääne-Harju Parish E497859 entity
Predicate contains P35 FINISHED
Object Paldiski 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: Paldiski | Statement: [Lääne-Harju Parish, contains, Paldiski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paldiski
Context triple: [Lääne-Harju Parish, contains, Paldiski]
  • A. Paldiski chosen
    Paldiski is a coastal town and former Soviet naval base in northwestern Estonia, located on the Pakri Peninsula by the Baltic Sea.
  • B. Jelgava
    Jelgava is a city in central Latvia known for its historic Jelgava Palace and role as a regional cultural and educational center.
  • C. Vasai
    Vasai is a historic coastal town in western India, near Mumbai, known for its strategic importance under Portuguese and later British rule and as the site of the 1802 Treaty of Bassein.
  • D. Pāvilosta
    Pāvilosta is a small coastal town in western Latvia known for its Baltic Sea beaches, fishing heritage, and laid-back seaside atmosphere.
  • E. Ventspils
    Ventspils is a port city on Latvia’s Baltic Sea coast known for its major ice-free harbor, oil and cargo terminals, and well-preserved historic center.
  • 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_69e0b4a5b7908190a972e4e7e698ae94 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e678b0ee708190bdbe4aab28a61525 completed April 20, 2026, 7:04 p.m.
Created at: April 16, 2026, 11:27 a.m.