Triple
T13704724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oculus Go |
E328609
|
entity |
| Predicate | headTrackingDegreesOfFreedom |
P28226
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Oculus Go, headTrackingDegreesOfFreedom, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headTrackingDegreesOfFreedom Context triple: [Oculus Go, headTrackingDegreesOfFreedom, 3]
-
A.
hasHeadPosition
Indicates the specific spatial position or orientation of an entity’s head relative to a reference frame or context.
-
B.
headMobility
Indicates the degree to which an entity’s head can move or be moved relative to its body.
-
C.
gimbalCapability
Indicates the ability of a system or device to support and control a gimbal’s movement or stabilization functions.
-
D.
hasDegreeOfFreedom
chosen
Indicates that one entity possesses a specific independent parameter or mode in which it can vary or move relative to another entity or within a system.
-
E.
hasRotationFrequency
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.