Triple
T36691221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CP-340 hard disk drive series |
E905960
|
entity |
| Predicate | storageDeviceType |
P136154
|
FINISHED |
| Object | hard disk 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: hard disk drive | Statement: [CP-340 hard disk drive series, storageDeviceType, hard disk drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageDeviceType Context triple: [CP-340 hard disk drive series, storageDeviceType, hard disk drive]
-
A.
storageDevice
Indicates a relationship where one entity functions as a device used to store data or digital information for another entity.
-
B.
storageCapacityType
Indicates the type or category of storage capacity associated with an entity (e.g., total, used, available, or reserved capacity).
-
C.
diskType
chosen
Indicates the specific kind or category of disk associated with or used by an entity.
-
D.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
E.
storageMechanism
Indicates the method or system by which something is stored, preserved, or kept for later use.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7e6b3f481909ad2b44e11f578f2 |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.