Triple
T13811375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculus Quest |
E331896
|
entity |
| Predicate | supportsRoomScale |
P111570
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Oculus Quest, supportsRoomScale, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRoomScale Context triple: [Oculus Quest, supportsRoomScale, yes]
-
A.
supportsSpatialAudioWith
Indicates that one entity is compatible with and can provide or enable spatial audio functionality when used with another entity.
-
B.
supportsMultiRoomAudio
Indicates that the subject is capable of playing synchronized audio across multiple rooms or speakers simultaneously.
-
C.
hasMotionControls
Indicates that an entity supports or involves control through physical movement or gestures rather than (or in addition to) traditional input methods.
-
D.
supportsHardwareRayTracing
Indicates that one entity provides or enables hardware-level ray tracing capabilities for another entity or within a given context.
-
E.
supportsStereoPairing
Indicates that an entity is capable of being paired with another similar entity to function together as a synchronized stereo audio system.
- F. None of above. chosen
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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026ff6b481908066d6bf27064417 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:12 p.m.