Triple
T29689752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperbola GNU/Linux-libre |
E751181
|
entity |
| Predicate | removesBinaryBlobsFromKernel |
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, removesBinaryBlobsFromKernel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removesBinaryBlobsFromKernel Context triple: [Hyperbola GNU/Linux-libre, removesBinaryBlobsFromKernel, yes]
-
A.
kernelConsistsOf
Indicates that a kernel is composed of or made up from the specified constituent elements or components.
-
B.
typicalKernelABI
Indicates that one entity uses or conforms to the other entity as its standard or default kernel-level application binary interface (ABI).
-
C.
abolishesBody
Indicates that one entity formally ends, eliminates, or does away with another entity or institutional body.
-
D.
removedBefore
Indicates that one entity was removed or taken away earlier in time than another specified entity or event.
-
E.
removedDuringMission
Indicates that an entity was taken away, detached, or eliminated while a mission or operation was in progress.
- 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_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 28, 2026, 7:15 p.m.