Triple
T28771360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vive Focus |
E726420
|
entity |
| Predicate | supports3DoFController |
P74469
|
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, supports3DoFController, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supports3DoFController Context triple: [Vive Focus, supports3DoFController, yes]
-
A.
hasMotionControls
Indicates that an entity supports or involves control through physical movement or gestures rather than (or in addition to) traditional input methods.
-
B.
supportsControllerInput
chosen
Indicates that an entity is capable of receiving and handling input from a controller device.
-
C.
gimbalCapability
Indicates the ability of a system or device to support and control a gimbal’s movement or stabilization functions.
-
D.
supports3DPerspective
Indicates that one entity provides or enables three-dimensional perspective viewing or rendering capabilities for another.
-
E.
supports3DTransforms
Indicates that one entity provides or is compatible with three-dimensional transform capabilities for another entity or within a given context.
- 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_6a01d077dcec8190b05b24b5de313b15 |
completed | May 11, 2026, 12:50 p.m. |
| PD | Predicate disambiguation | batch_6a01cea0e37881909cb6888518c6d12f |
completed | May 11, 2026, 12:42 p.m. |
Created at: April 28, 2026, 6:16 a.m.