Triple
T37665652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switch 2 |
E937813
|
entity |
| Predicate | hasStorageDetails |
P105108
|
FINISHED |
| Object | unconfirmed (as of 2024) |
—
|
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: unconfirmed (as of 2024) | Statement: [Switch 2, hasStorageDetails, unconfirmed (as of 2024)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorageDetails Context triple: [Switch 2, hasStorageDetails, unconfirmed (as of 2024)]
-
A.
hasStorage
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
B.
storageProperty
chosen
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
-
C.
hasStorageFunction
Indicates that an entity serves to store, retain, or hold another entity or resource for later use.
-
D.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
E.
hasStorageClass
Indicates that one entity is assigned or associated with a particular storage class that defines how its data is stored or managed.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a008b8938608190adaccbd720111a18 |
completed | May 10, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_6a008b24baac8190baaaf50c2e9cc6bd |
completed | May 10, 2026, 1:41 p.m. |
Created at: May 3, 2026, 4:18 p.m.