Triple

T13319937
Position Surface form Disambiguated ID Type / Status
Subject SOIC-8 E317286 entity
Predicate hasThermalCharacteristic P109510 FINISHED
Object lower thermal mass than DIP-8 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: lower thermal mass than DIP-8 | Statement: [SOIC-8, hasThermalCharacteristic, lower thermal mass than DIP-8]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasThermalCharacteristic
Context triple: [SOIC-8, hasThermalCharacteristic, lower thermal mass than DIP-8]
  • A. hasThermalActivity
    Indicates that an entity exhibits or is associated with heat-related phenomena such as heating, cooling, or temperature change.
  • B. hasThermalEstablishment
    Indicates that one entity is responsible for creating, setting, or defining the thermal conditions or temperature state of another entity.
  • C. usesThermals
    Indicates that one entity relies on rising warm air currents (thermals) as a means to gain lift, move, or maintain altitude.
  • D. hasTemperature
    Indicates that an entity possesses or is characterized by a specific temperature value.
  • E. hasTemperatureRegime
    Indicates that an entity is characterized by or associated with a particular pattern or regime of temperature conditions.
  • 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_69d806b4d62c81908d4ced1665414be5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99cfdc9388190af1fdd3cd4717bd8 completed April 11, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69d98f6babd88190a5d529df9584b9a4 completed April 11, 2026, 12:01 a.m.
PDg Predicate description generation batch_69d99cf7f9c48190a6a4f452b4a2aefa completed April 11, 2026, 12:59 a.m.
Created at: April 9, 2026, 9:29 p.m.