Triple
T15939756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQA |
E386526
|
entity |
| Predicate | playableAs |
P72061
|
FINISHED |
| Object | standard PCM on non-MQA devices |
—
|
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: standard PCM on non-MQA devices | Statement: [MQA, playableAs, standard PCM on non-MQA devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableAs Context triple: [MQA, playableAs, standard PCM on non-MQA devices]
-
A.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
B.
playableMode
Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
-
C.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
D.
canAlsoBePlayedIn
chosen
Indicates that something (such as a game, media, or activity) is additionally playable or usable in another context, format, or environment beyond its primary one.
-
E.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.