Triple

T16055795
Position Surface form Disambiguated ID Type / Status
Subject Tômbua-Lândana E389476 entity
Predicate offshoreOnshore P72209 FINISHED
Object offshore LITERAL 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: offshore | Statement: [Tômbua-Lândana, offshoreOnshore, offshore]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offshoreOnshore
Context triple: [Tômbua-Lândana, offshoreOnshore, offshore]
  • A. onshoreOrOffshore chosen
    Indicates whether something is located or occurring on land (onshore) or at sea/away from land (offshore).
  • B. offshoreUnit
    Indicates that one entity is an offshore facility or installation associated with, located near, or operating in relation to another entity (such as a geographic area, project, or jurisdiction).
  • C. locatedOffshoreOf
    Indicates that one entity is situated in an offshore area (typically at sea) relative to another, such as off the coast or maritime boundary of that reference entity.
  • D. offshoreFeature
    Indicates that a geographic or structural feature is located in a marine or aquatic area away from the shoreline.
  • E. isOffshoreVersionOf
    Indicates that one entity is a version or counterpart of another that is located, registered, or operated in an offshore jurisdiction.
  • F. None of above.

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_69d86dae698881908327ef2d67706cb9 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1858a00888190b8505071575dc56f completed April 17, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69e18272f2288190a17d45fb01cc2b07 completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 4:56 a.m.