Triple
T29689776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperbola GNU/Linux-libre |
E751181
|
entity |
| Predicate | removesNonFreeFirmwareFromKernel |
P168671
|
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, removesNonFreeFirmwareFromKernel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removesNonFreeFirmwareFromKernel Context triple: [Hyperbola GNU/Linux-libre, removesNonFreeFirmwareFromKernel, yes]
-
A.
removesBinaryBlobsFromKernel
chosen
Indicates that an entity eliminates or strips out binary blob components from a kernel.
-
B.
removesDRMRelatedComponents
Indicates that an entity eliminates or strips out components associated with digital rights management (DRM) from another entity.
-
C.
firmware
Indicates that one entity serves as the firmware (embedded low-level control software) for another entity.
-
D.
kernelConsistsOf
Indicates that a kernel is composed of or made up from the specified constituent elements or components.
-
E.
associatedWithFirmware
Indicates a relationship where an entity is linked or connected to specific firmware, such as being used by, dependent on, or relevant to that firmware.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 7:15 p.m.