Triple
T30114244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation TV |
E765368
|
entity |
| Predicate | supportsRemotePlayFrom |
P33103
|
FINISHED |
| Object | PlayStation 4 |
E42441
|
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 4 | Statement: [PlayStation TV, supportsRemotePlayFrom, PlayStation 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRemotePlayFrom Context triple: [PlayStation TV, supportsRemotePlayFrom, PlayStation 4]
-
A.
supportsRemotePlay
chosen
Indicates that one entity enables or is compatible with remote play functionality for another entity.
-
B.
supportsAirPlay
Indicates that one entity is capable of sending or receiving media via Apple’s AirPlay streaming protocol in relation to another entity.
-
C.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
-
D.
tvPlaySupport
Indicates that one entity provides support or assistance in the production, airing, or operation of a television play or TV program for another entity.
-
E.
supportsInstantPlay
Indicates that one entity enables or is compatible with immediate, on-demand use or playback of another entity without requiring prior download or installation.
- 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_6a277bfb2aa48190a4901d811532e941 |
completed | June 9, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:11 p.m.