Triple
T2447889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Performa 5200CD |
E53635
|
entity |
| Predicate | opticalDriveType |
P33101
|
FINISHED |
| Object | 4x CD-ROM drive |
—
|
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: 4x CD-ROM drive | Statement: [Performa 5200CD, opticalDriveType, 4x CD-ROM drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalDriveType Context triple: [Performa 5200CD, opticalDriveType, 4x CD-ROM drive]
-
A.
opticalDrive
chosen
Indicates that one entity functions as an optical drive (e.g., CD/DVD/Blu-ray reader/writer) for another entity.
-
B.
opticalDiscType
Indicates the specific kind or category of an optical disc involved in the relationship (e.g., CD, DVD, Blu-ray).
-
C.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
D.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
E.
hasFloppyDrive
Indicates that an entity is equipped with or includes a floppy disk drive.
- 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0aed2688190a18fe66b98d80e0b |
completed | March 7, 2026, 7:15 a.m. |
Created at: March 6, 2026, 9:43 p.m.