Triple
T28771377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vive Focus |
E726420
|
entity |
| Predicate | supportsHeadTracking |
P180839
|
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: [Vive Focus, supportsHeadTracking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHeadTracking Context triple: [Vive Focus, supportsHeadTracking, yes]
-
A.
supportsTrackingSystem
chosen
Indicates that an entity provides compatibility with, or functionality for, a tracking system, enabling items or activities to be monitored or recorded.
-
B.
supportsRoomScale
Indicates that an entity provides compatibility with or functionality for room-scale operation or experiences.
-
C.
supportsPCVRConnection
Indicates that an entity enables or is compatible with establishing a PC-based virtual reality (VR) connection.
-
D.
hasOculus
Indicates that one entity possesses or is equipped with an oculus (a circular opening or eye-like feature).
-
E.
gimbalCapability
Indicates the ability of a system or device to support and control a gimbal’s movement or stabilization functions.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01e3a2d0e08190a7d5622920dc56e6 |
completed | May 11, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_6a01e3013e7881909f0cdca25a53c009 |
completed | May 11, 2026, 2:09 p.m. |
Created at: April 28, 2026, 6:16 a.m.