Triple
T36691079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toshiba P300 |
E905956
|
entity |
| Predicate | dataStorageFunction |
P82748
|
FINISHED |
| Object | mass storage |
—
|
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: mass storage | Statement: [Toshiba P300, dataStorageFunction, mass storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataStorageFunction Context triple: [Toshiba P300, dataStorageFunction, mass storage]
-
A.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
B.
hasStorageFunction
chosen
Indicates that an entity serves to store, retain, or hold another entity or resource for later use.
-
C.
storageMechanism
Indicates the method or system by which something is stored, preserved, or kept for later use.
-
D.
storageInterface
Indicates that one entity serves as a storage interface used by or associated with another entity for storing or retrieving data.
-
E.
dataManagement
Indicates the relationship in which an entity organizes, stores, maintains, and governs data throughout its lifecycle.
- 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_69f7c7c767cc81909fbed9de6af09e55 |
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.