Triple

T29689562
Position Surface form Disambiguated ID Type / Status
Subject gNewSense E751176 entity
Predicate bootFirmwarePolicy P167595 FINISHED
Object discourages use of non-free BIOS or firmware 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: discourages use of non-free BIOS or firmware | Statement: [gNewSense, bootFirmwarePolicy, discourages use of non-free BIOS or firmware]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bootFirmwarePolicy
Context triple: [gNewSense, bootFirmwarePolicy, discourages use of non-free BIOS or firmware]
  • A. typicalOSUpdatePolicy
    Indicates the usual or standard policy governing how operating system updates are obtained, scheduled, and applied.
  • B. implementedPolicy
    Indicates that a particular policy has been put into effect or carried out by an entity.
  • C. establishedPolicy
    Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
  • D. governingPolicy
    Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
  • E. appliesPolicyType
    Indicates that a specific policy type is applied to or enforced on a given entity or context.
  • 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_69f672938e18819082394196f97e6340 completed May 2, 2026, 9:54 p.m.
PD Predicate disambiguation batch_69f6659f246081909821c5f452d14e8f completed May 2, 2026, 8:59 p.m.
PDg Predicate description generation batch_69f6691da93081909deaf680614fc900 completed May 2, 2026, 9:14 p.m.
Created at: April 28, 2026, 7:15 p.m.