Triple
T1892070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation 5 |
E41894
|
entity |
| Predicate | internalStorageCapacity |
P26320
|
FINISHED |
| Object | 825 GB |
—
|
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: 825 GB | Statement: [PlayStation 5, internalStorageCapacity, 825 GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalStorageCapacity Context triple: [PlayStation 5, internalStorageCapacity, 825 GB]
-
A.
installedCapacity
Indicates the maximum output or production capability that has been set up or built for a system, facility, or equipment, typically measured under specified conditions.
-
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.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
D.
totalSpace
chosen
Indicates the overall amount of space or capacity available or occupied by an entity or within a given context.
-
E.
interiorSize
Indicates the size or dimensions of the inside space of an object or structure.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb145f96c8190a71bb9e442892e68 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.