Triple
T29390199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SDXC |
E745351
|
entity |
| Predicate | supportsCapacityRange |
P35147
|
FINISHED |
| Object | 32 GB to 2 TB |
—
|
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: 32 GB to 2 TB | Statement: [SDXC, supportsCapacityRange, 32 GB to 2 TB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCapacityRange Context triple: [SDXC, supportsCapacityRange, 32 GB to 2 TB]
-
A.
offersCapacityRange
chosen
Indicates that an entity provides or makes available a service, product, or resource whose capacity is specified as a range between a minimum and maximum value.
-
B.
hasCapacityTo
Indicates that one entity possesses the ability, power, or potential to perform an action or bring about a particular effect in relation to another entity or context.
-
C.
hasCapacityType
Indicates that an entity possesses a specific kind or classification of capacity or capability.
-
D.
logicCapacityRange
Indicates the range of logical processing or reasoning capacity that an entity can handle or support.
-
E.
rangeCapability
Indicates the maximum distance or extent over which an entity can effectively operate, function, or exert its effect.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a034540e37c819087a5c75c559323d8 |
completed | May 12, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a0344e26fec8190867227f9692e92df |
completed | May 12, 2026, 3:18 p.m. |
Created at: April 28, 2026, 2:41 p.m.