Triple
T31819957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LeftHand Networks |
E812231
|
entity |
| Predicate | storageArchitecture |
P37901
|
FINISHED |
| Object | scale-out 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: scale-out storage | Statement: [LeftHand Networks, storageArchitecture, scale-out storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageArchitecture Context triple: [LeftHand Networks, storageArchitecture, scale-out storage]
-
A.
storageTechnology
chosen
Indicates the type or method of data storage technology used or associated with an entity.
-
B.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
-
C.
storageMechanism
Indicates the method or system by which something is stored, preserved, or kept for later use.
-
D.
storageOrgan
Indicates that one entity serves as a storage organ (a specialized structure for storing substances like nutrients or water) for another entity.
-
E.
storageDevice
Indicates a relationship where one entity functions as a device used to store data or digital information 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6af7f24a881909e6ae0d937e90ea2 |
completed | May 3, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:45 p.m.