Triple
T13848472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculus Quest 2 |
E332870
|
entity |
| Predicate | supportsHandTracking |
P40440
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oculus Quest 2, supportsHandTracking, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHandTracking Context triple: [Oculus Quest 2, supportsHandTracking, true]
-
A.
hasMotionControls
chosen
Indicates that an entity supports or involves control through physical movement or gestures rather than (or in addition to) traditional input methods.
-
B.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
C.
supportsRealTimeEyeAF
Indicates that the subject provides real-time autofocus functionality specifically for tracking and focusing on a subject’s eyes.
-
D.
supportsARFilters
Indicates that one entity provides or enables augmented reality (AR) filter functionality for another entity or within a given context.
-
E.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b2a9788190b164760adec64ef6 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.