Triple
T8724257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linux kernel |
E207089
|
entity |
| Predicate | supportsLoadableKernelModules |
P38742
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Linux kernel, supportsLoadableKernelModules, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLoadableKernelModules Context triple: [Linux kernel, supportsLoadableKernelModules, true]
-
A.
hasKernel
Indicates that one entity functions as the kernel (core or central component) of another entity.
-
B.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
C.
supportsModule
chosen
Indicates that one entity provides compatibility, functionality, or resources necessary for another entity’s module to operate or be used.
-
D.
supportsInitrd
Indicates that one entity provides the capability to load, use, or work with an initial RAM disk (initrd) for another entity.
-
E.
hasKernelType
Indicates that an entity possesses or is associated with a specific type or classification of kernel.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d1404948190bc45d14a1ddb1a7e |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.