Triple

T12026296
Position Surface form Disambiguated ID Type / Status
Subject Océanopolis E286285 entity
Predicate locatedNear P294 FINISHED
Object Brest harbour E270377 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: Brest harbour | Statement: [Océanopolis, locatedNear, Brest harbour]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brest harbour
Context triple: [Océanopolis, locatedNear, Brest harbour]
  • A. Brest naval base chosen
    Brest naval base is a major French naval installation on the Atlantic coast that serves as a key home port and operational hub for France’s surface fleet.
  • B. Baltiysk seaport
    Baltiysk seaport is a major Russian Baltic Sea port and naval base located near the Vistula Spit in the Kaliningrad Oblast.
  • C. Skadovsk Port
    Skadovsk Port is a Ukrainian seaport on the Black Sea that serves as a regional maritime hub for cargo and passenger transport in Kherson Oblast.
  • D. Port Pivdennyi
    Port Pivdennyi is a major deep-water seaport on Ukraine’s Black Sea coast, serving as a key hub for bulk cargo and international maritime trade.
  • E. Yalta Sea Port
    Yalta Sea Port is a major maritime harbor and transportation hub serving the resort city of Yalta on the southern coast of the Crimean Peninsula.
  • 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_69d6ab4669e48190b59246358b0383ab completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903f02638819091e0cc0e93fa5ea7 completed April 10, 2026, 2:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6345319808190a68195e215c2bd80 completed May 2, 2026, 5:28 p.m.
Created at: April 8, 2026, 9:47 p.m.