Triple
T10067860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation Network |
E213143
|
entity |
| Predicate | outage |
P3823
|
FINISHED |
| Object | 2011-04-20 to 2011-05-14 |
—
|
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: 2011-04-20 to 2011-05-14 | Statement: [PlayStation Network, outage, 2011-04-20 to 2011-05-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outage Context triple: [PlayStation Network, outage, 2011-04-20 to 2011-05-14]
-
A.
powerOutages
Indicates that there is a loss or interruption of electrical power supply affecting one or more entities or locations.
-
B.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
C.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
D.
fallEvent
Indicates an event in which an entity loses balance or support and moves downward, typically resulting in a fall.
-
E.
notableInfrastructureFailure
chosen
Indicates that a significant piece of infrastructure has failed or malfunctioned in a way that disrupts its normal operation or intended service.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcff798bc8190a84af7bedea66f0a |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:58 p.m.