Triple

T29689775
Position Surface form Disambiguated ID Type / Status
Subject Hyperbola GNU/Linux-libre E751181 entity
Predicate supportsLibrebootHardware P207166 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: [Hyperbola GNU/Linux-libre, supportsLibrebootHardware, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsLibrebootHardware
Context triple: [Hyperbola GNU/Linux-libre, supportsLibrebootHardware, yes]
  • A. supportsUEFIBoot
    Indicates that an entity is capable of initiating or handling the system startup process using UEFI (Unified Extensible Firmware Interface) boot mode.
  • B. supportsIntelBootGuard
    Indicates that one entity provides compatibility with or implementation of Intel Boot Guard functionality for another entity.
  • C. supportsSecureBoot
    Indicates that an entity is capable of enabling or operating with secure boot mechanisms that verify software integrity during the startup process.
  • D. hasHardwareCompatibilityWith
    Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
  • E. hasBIOSReplacement
    Indicates that one BIOS component or configuration is designated to replace another.
  • 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_69f0d625b09481909b0b69aea1e846c8 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e0f3d88190a4ee7b0673f1ef90 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c7ee0388190a29faeb5cdb0950a completed May 12, 2026, 7:16 p.m.
Created at: April 28, 2026, 7:15 p.m.