Triple
T1892066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation 5 |
E41894
|
entity |
| Predicate | gpuComputePerformance |
P33100
|
FINISHED |
| Object | 10.28 TFLOPS |
—
|
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: 10.28 TFLOPS | Statement: [PlayStation 5, gpuComputePerformance, 10.28 TFLOPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gpuComputePerformance Context triple: [PlayStation 5, gpuComputePerformance, 10.28 TFLOPS]
-
A.
gpuType
Indicates the specific kind or model category of GPU associated with an entity.
-
B.
neuralEnginePerformance
Indicates the level or efficiency of processing capability provided by a neural engine in performing AI or machine-learning tasks.
-
C.
gpuCoreCount
Indicates the number of processing cores present in a GPU.
-
D.
performanceCores
Indicates a relationship where certain cores within a processor are designated as high-performance cores optimized for speed and intensive tasks.
-
E.
integratesGPU
Indicates that one entity incorporates or embeds a GPU as a functional component within its design or system.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69abb11bfd2c8190a805372589f73238 |
completed | March 7, 2026, 5:01 a.m. |
Created at: March 4, 2026, 7:34 p.m.