Triple

T30616310
Position Surface form Disambiguated ID Type / Status
Subject Human Torch E779324 entity
Predicate canControlAmbientHeat P23545 FINISHED
Object true 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: true | Statement: [Human Torch, canControlAmbientHeat, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canControlAmbientHeat
Context triple: [Human Torch, canControlAmbientHeat, true]
  • A. thermalControl chosen
    Indicates a relationship where one entity regulates, adjusts, or maintains the temperature or thermal conditions of another entity or environment.
  • B. climateControlFeature
    Indicates that an entity includes or supports a function or system for regulating environmental conditions such as temperature, humidity, or airflow.
  • C. temperatureControlMethod
    Indicates the method or mechanism used to regulate or maintain a desired temperature.
  • D. hasEnvironmentalControl
    Indicates that one entity regulates, influences, or manages the environmental conditions affecting another entity or area.
  • E. hasEnvironmentalControls
    Indicates that one entity provides or is equipped with systems or mechanisms to regulate environmental conditions (such as temperature, humidity, or air quality) for another entity or space.
  • 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_69f224a3307081909a6dca8ca75dbf48 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68a16debc8190a12f5f65ced055d7 completed May 2, 2026, 11:34 p.m.
PD Predicate disambiguation batch_69f6860def1c81909d79e1f088c4b5e5 completed May 2, 2026, 11:17 p.m.
Created at: April 29, 2026, 8:26 p.m.