Triple

T27918395
Position Surface form Disambiguated ID Type / Status
Subject San Juan Basin E706135 entity
Predicate majorHydrocarbonPlay P43884 FINISHED
Object yes 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: yes | Statement: [San Juan Basin, majorHydrocarbonPlay, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: majorHydrocarbonPlay
Context triple: [San Juan Basin, majorHydrocarbonPlay, yes]
  • A. discoveredAsPetroleumPlay
    Indicates that the subject was identified or recognized specifically as a viable petroleum exploration or production opportunity.
  • B. hydrocarbonPotential chosen
    Indicates the degree to which a geological unit or material is capable of generating, containing, or yielding hydrocarbons such as oil or natural gas.
  • C. primaryHydrocarbonType
    Indicates the main or dominant type of hydrocarbon associated with an entity, such as a resource, sample, or reservoir.
  • D. primaryHydrocarbon
    Indicates that one entity is a primary hydrocarbon, typically meaning it has a carbon atom bonded to only one other carbon within the molecular structure.
  • E. discoveredHydrocarbons
    Indicates that an entity has found or identified the presence of hydrocarbons in or associated with another entity or location.
  • 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_69ef96b6cc808190aab19fb18b235f4b completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69fd05ba6b2c81909c62b46237d10365 completed May 7, 2026, 9:35 p.m.
PD Predicate disambiguation batch_69fd03039e48819082b6e12c5453885a completed May 7, 2026, 9:24 p.m.
Created at: April 27, 2026, 6:55 p.m.