Triple
T2567954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreeDOS |
E57594
|
entity |
| Predicate | bootableFrom |
P31985
|
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: [FreeDOS, bootableFrom, floppy disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bootableFrom Context triple: [FreeDOS, bootableFrom, floppy disk]
-
A.
bootMedium
chosen
Indicates that one entity serves as the medium or device from which another entity is booted or started.
-
B.
bootLoader
Indicates that one entity functions as the boot loader responsible for initializing or starting up another entity (such as a system, device, or software environment).
-
C.
supportsInstallationMedia
Indicates that one entity is capable of accepting, handling, or working with a specified type of installation media for setup or deployment purposes.
-
D.
installationMedia
Indicates that something serves as or is used as the medium (such as a disk, image, or package) through which a software or system is installed.
-
E.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd36191848190b6255fa9029429bd |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.