Triple
T30114246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation TV |
E765368
|
entity |
| Predicate | supportsDigitalDistributionService |
P79779
|
FINISHED |
| Object | PlayStation Store |
E234525
|
NE 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: PlayStation Store | Statement: [PlayStation TV, supportsDigitalDistributionService, PlayStation Store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDigitalDistributionService Context triple: [PlayStation TV, supportsDigitalDistributionService, PlayStation Store]
-
A.
hasDigitalDistribution
Indicates that something is made available or delivered through electronic or online channels rather than through physical media.
-
B.
supportsDigitalDownloads
chosen
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
-
C.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
D.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
E.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
- F. None of above.
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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2743393f9c819089ac53a51e56df18 |
completed | June 8, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:11 p.m.