Triple

T28039189
Position Surface form Disambiguated ID Type / Status
Subject Viking Graben E708490 entity
Predicate developedForOffshoreProductionIn P174362 FINISHED
Object 1970s 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: 1970s | Statement: [Viking Graben, developedForOffshoreProductionIn, 1970s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: developedForOffshoreProductionIn
Context triple: [Viking Graben, developedForOffshoreProductionIn, 1970s]
  • A. offshoreFeature
    Indicates that a geographic or structural feature is located in a marine or aquatic area away from the shoreline.
  • B. onshoreOrOffshore
    Indicates whether something is located or occurring on land (onshore) or at sea/away from land (offshore).
  • C. offshoreProcessingLocation
    Indicates that an action, service, or operation is carried out at a location situated offshore, typically outside the primary or originating jurisdiction.
  • D. worksOnProduction
    Indicates that an entity is actively involved in or assigned to work on a specific production (such as a film, show, or project).
  • E. hasProductionFacilitiesIn
    Indicates that an entity operates or owns production facilities located within a specified geographic area or jurisdiction.
  • 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_69ef9b6cf538819094a633ffa67afec1 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f6c20f209081909fb9ac8f95069f04 completed May 3, 2026, 3:33 a.m.
PD Predicate disambiguation batch_69f6bd2415fc81908c23c311aebce66f completed May 3, 2026, 3:12 a.m.
PDg Predicate description generation batch_69f6c125695c81909704c67bef4ce5b2 completed May 3, 2026, 3:29 a.m.
Created at: April 27, 2026, 8:23 p.m.