Triple
T12728393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 600 |
E304165
|
entity |
| Predicate | hardDiskInterface |
P96767
|
FINISHED |
| Object | SCSI |
—
|
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: SCSI | Statement: [Macintosh Performa 600, hardDiskInterface, SCSI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardDiskInterface Context triple: [Macintosh Performa 600, hardDiskInterface, SCSI]
-
A.
hardDriveInterface
chosen
Indicates the type of connection standard or protocol through which a hard drive communicates with a computer or controller.
-
B.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
C.
hasSATA
Indicates that one entity possesses, includes, or is equipped with a SATA (Serial ATA) interface or connection in relation to another entity.
-
D.
standardHardDiskCapacity
Indicates the typical or nominal storage capacity of a hard disk as defined by a given standard or specification.
-
E.
opticalDrive
Indicates that one entity functions as an optical drive (e.g., CD/DVD/Blu-ray reader/writer) for 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.