Triple
T28771375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vive Focus |
E726420
|
entity |
| Predicate | supports360Video |
P203738
|
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, supports360Video, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supports360Video Context triple: [Vive Focus, supports360Video, yes]
-
A.
supportsVerticalVideo
Indicates that one entity provides compatibility with or proper handling of vertical (portrait-oriented) video content for another entity.
-
B.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
-
C.
supports4KVideoRecording
Indicates that the subject is capable of recording video at 4K (Ultra HD) resolution.
-
D.
supportsH264
Indicates that one entity provides compatibility with, or the ability to encode/decode or process, H.264 video for another entity.
-
E.
supports3DPerspective
Indicates that one entity provides or enables three-dimensional perspective viewing or rendering capabilities for another.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01d9ca07b88190b4ad70b6336447b6 |
completed | May 11, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_6a01d807c3048190b79f0b6b933dd3b7 |
completed | May 11, 2026, 1:22 p.m. |
| PDg | Predicate description generation | batch_6a01d9c926508190936f05ce4a19c20d |
completed | May 11, 2026, 1:29 p.m. |
Created at: April 28, 2026, 6:16 a.m.