Triple
T9945414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LILO |
E195191
|
entity |
| Predicate | supportsBootDevice |
P31893
|
FINISHED |
| Object | floppy 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: floppy disk | Statement: [LILO, supportsBootDevice, floppy disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBootDevice Context triple: [LILO, supportsBootDevice, floppy disk]
-
A.
supportsSecureBoot
Indicates that an entity is capable of enabling or operating with secure boot mechanisms that verify software integrity during the startup process.
-
B.
supportsUEFIBoot
Indicates that an entity is capable of initiating or handling the system startup process using UEFI (Unified Extensible Firmware Interface) boot mode.
-
C.
supportsIntelBootGuard
Indicates that one entity provides compatibility with or implementation of Intel Boot Guard functionality for another entity.
-
D.
supportsInstallationMedia
chosen
Indicates that one entity is capable of accepting, handling, or working with a specified type of installation media for setup or deployment purposes.
-
E.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb61561848190aba7250f3b3c4ed5 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.