Triple
T37409710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Macintosh 8600 |
E929527
|
entity |
| Predicate | hardDrive |
P16222
|
FINISHED |
| Object | internal SCSI 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: internal SCSI hard disk | Statement: [Power Macintosh 8600, hardDrive, internal SCSI hard disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardDrive Context triple: [Power Macintosh 8600, hardDrive, internal SCSI hard disk]
-
A.
hardDriveInterface
Indicates the type of connection standard or protocol through which a hard drive communicates with a computer or controller.
-
B.
mechanicalDrive
Indicates a relationship where one entity transmits mechanical power or motion to another, typically via components like gears, belts, or shafts.
-
C.
hasInternalHardDrive
chosen
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
D.
standardHardDiskCapacity
Indicates the typical or nominal storage capacity of a hard disk as defined by a given standard or specification.
-
E.
supportsDiskDrives
Indicates that one entity is capable of accommodating, operating, or being compatible with disk drives associated with 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.