Triple

T32774552
Position Surface form Disambiguated ID Type / Status
Subject Estonia E838158 entity
Predicate hasTerritorialSeaIn P193729 FINISHED
Object Gulf of Finland 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: Gulf of Finland | Statement: [Estonia, hasTerritorialSeaIn, Gulf of Finland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTerritorialSeaIn
Context triple: [Estonia, hasTerritorialSeaIn, Gulf of Finland]
  • A. claimedAsTerritorialSeaBy
    Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
  • B. separatesTerritorialWatersOf
    Indicates that one entity (typically a body of water or boundary) serves as a dividing line between the territorial waters of two or more distinct entities.
  • C. hasLandBorderWithSea
    Indicates that an entity’s land area directly borders or touches a sea along its coastline.
  • D. hasCoastlineOn
    Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
  • E. hasCountryCoastlineOn
    Indicates that a country has a coastline bordering a specified body of water or sea.
  • F. None of above. chosen

Provenance (4 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_69f3493a824c8190938489ba69041d08 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fd509e6bc08190b263923c2f40fea3 completed May 8, 2026, 2:55 a.m.
PD Predicate disambiguation batch_69fd4fd1a58881909d4b84de1b24e380 completed May 8, 2026, 2:52 a.m.
PDg Predicate description generation batch_69fd509cdc5c8190a5f2c451bc0d0b25 completed May 8, 2026, 2:55 a.m.
Created at: May 1, 2026, 1:13 a.m.