Triple

T3055039
Position Surface form Disambiguated ID Type / Status
Subject Solar Orbiter mission E60458 entity
Predicate thermalProtection P14978 FINISHED
Object heat shield for close solar approach 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: heat shield for close solar approach | Statement: [Solar Orbiter mission, thermalProtection, heat shield for close solar approach]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: thermalProtection
Context triple: [Solar Orbiter mission, thermalProtection, heat shield for close solar approach]
  • A. thermalControl
    Indicates a relationship where one entity regulates, adjusts, or maintains the temperature or thermal conditions of another entity or environment.
  • B. heatShieldType chosen
    Indicates the specific kind or category of heat shield associated with an object or system.
  • C. protectionType
    Indicates the kind or method of protection that is applied to or associated with an entity.
  • D. hasThermalActivity
    Indicates that an entity exhibits or is associated with heat-related phenomena such as heating, cooling, or temperature change.
  • E. providesProtectionAgainst
    Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
  • 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_69ad8578137c81908259dcb27c7d6d7c completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ad9bf6b9948190bc957bfd1579c471 completed March 8, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69ad962195388190856013a2519c2b0f completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3:02 p.m.