Triple
T32481137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LInux LOader |
E830112
|
entity |
| Predicate | bootDeviceSupport |
P31985
|
FINISHED |
| Object | hard disk |
—
|
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: hard disk | Statement: [LInux LOader, bootDeviceSupport, hard disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootDeviceSupport Context triple: [LInux LOader, bootDeviceSupport, hard disk]
-
A.
bootFeature
Indicates that an entity provides or is associated with a specific feature or capability available at system boot time.
-
B.
bootMedium
chosen
Indicates that one entity serves as the medium or device from which another entity is booted or started.
-
C.
bootIndicator
Indicates that a system, device, or component is in a state or condition related to its startup or boot process.
-
D.
supportsIntelBootGuard
Indicates that one entity provides compatibility with or implementation of Intel Boot Guard functionality for another entity.
-
E.
supportsUEFIBoot
Indicates that an entity is capable of initiating or handling the system startup process using UEFI (Unified Extensible Firmware Interface) boot mode.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3962bd4819095fc94002d3f5247 |
completed | May 3, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:58 a.m.