Triple
T2108172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation 4 |
E42441
|
entity |
| Predicate | PlayStation 4 ProFeature |
P25458
|
FINISHED |
| Object | 4K rendering support |
—
|
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: 4K rendering support | Statement: [PlayStation 4, PlayStation 4 ProFeature, 4K rendering support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PlayStation 4 ProFeature Context triple: [PlayStation 4, PlayStation 4 ProFeature, 4K rendering support]
-
A.
equipmentCharacteristic
chosen
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
B.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
C.
supportsGameStreaming
Indicates that one entity provides the capability for another entity to stream and play games remotely in real time.
-
D.
supportsRemotePlay
Indicates that one entity enables or is compatible with remote play functionality for another entity.
-
E.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae03f308190841f5a419bb821f6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.