Triple
T11895647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation Now |
E283028
|
entity |
| Predicate | saveData |
P1596
|
FINISHED |
| Object | stored in cloud for streamed titles |
—
|
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: stored in cloud for streamed titles | Statement: [PlayStation Now, saveData, stored in cloud for streamed titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saveData Context triple: [PlayStation Now, saveData, stored in cloud for streamed titles]
-
A.
saveBy
Indicates that one entity preserves, rescues, or protects another entity from loss, harm, or danger.
-
B.
save
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
-
C.
saveSystem
Indicates performing an action that preserves or stores the current state or configuration of a system for future use or recovery.
-
D.
dataStorage
chosen
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
E.
savedWith
Indicates that one entity is preserved, stored, or kept together in association with another entity.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1286808190949719f54ff49a01 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.