Triple
T21268880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple DOS |
E524201
|
entity |
| Predicate | supportsSingleSidedDisks |
P83499
|
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: [Apple DOS, supportsSingleSidedDisks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSingleSidedDisks Context triple: [Apple DOS, supportsSingleSidedDisks, true]
-
A.
diskSidesSupported
chosen
Indicates how many and which sides of a disk the system or device is capable of reading from or writing to.
-
B.
storageCapacityDualLayerSingleSided
Indicates the amount of data that can be stored on a dual-layer, single-sided storage medium.
-
C.
supportsPhysicalMedia
Indicates that one entity provides the capability to use, read, or handle physical media formats (such as discs, tapes, or printed materials) associated with another entity.
-
D.
storageCapacityDualLayerDoubleSided
Indicates the total data storage capacity of a medium that uses dual layers on both sides (double-sided) for recording.
-
E.
hasSATA
Indicates that one entity possesses, includes, or is equipped with a SATA (Serial ATA) interface or connection in relation to another entity.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651115081908b5083ba818a6bb1 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:01 p.m.