Triple
T9000366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memory Stick |
E215024
|
entity |
| Predicate | maximumCapacityOriginalStandard |
P28148
|
FINISHED |
| Object | 128 MB |
—
|
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: 128 MB | Statement: [Memory Stick, maximumCapacityOriginalStandard, 128 MB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumCapacityOriginalStandard Context triple: [Memory Stick, maximumCapacityOriginalStandard, 128 MB]
-
A.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
officialCapacity
Indicates that an action or relationship is undertaken or held by an entity in their formal, authorized, or institutional role rather than in a personal capacity.
-
D.
originalCapacity
chosen
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
E.
totalCapacity
Indicates the maximum amount or volume that something can hold or accommodate in total.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6954bb1881908d004a26ba7fe360 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.