Triple

T3778907
Position Surface form Disambiguated ID Type / Status
Subject The Geysers geothermal field E83372 entity
Predicate geothermalResourceType P34678 FINISHED
Object vapor-dominated reservoir 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: vapor-dominated reservoir | Statement: [The Geysers geothermal field, geothermalResourceType, vapor-dominated reservoir]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: geothermalResourceType
Context triple: [The Geysers geothermal field, geothermalResourceType, vapor-dominated reservoir]
  • A. geologicType
    Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
  • B. hasGeothermalPotential
    Indicates that an entity possesses conditions suitable for generating or exploiting geothermal energy.
  • C. reservoirType chosen
    Indicates the specific kind or classification of a reservoir associated with an entity.
  • D. typeOfVolcanicFeature
    Indicates that one entity is classified as a specific kind or category of volcanic feature represented by the other entity.
  • E. hasTypeOfTectonicFeature
    Indicates that one entity is characterized by or classified as a specific type of tectonic feature (such as a fault, plate boundary, or rift).
  • 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_69ad8b235e608190b5a2b1d1bfcef50b completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcc78173081908b230017834cdf9e completed March 8, 2026, 7:22 p.m.
PD Predicate disambiguation batch_69adc050cc5c81909d9855f866f3c26d completed March 8, 2026, 6:30 p.m.
Created at: March 8, 2026, 3:36 p.m.