Triple
T28771372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vive Focus |
E726420
|
entity |
| Predicate | requiresExternalTrackingCameras |
P111572
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Vive Focus, requiresExternalTrackingCameras, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresExternalTrackingCameras Context triple: [Vive Focus, requiresExternalTrackingCameras, no]
-
A.
supportsTrackingSystem
Indicates that an entity provides compatibility with, or functionality for, a tracking system, enabling items or activities to be monitored or recorded.
-
B.
requiresExternalSensors
chosen
Indicates that performing this action or maintaining this relationship depends on input or data from sensors that are external to the entity itself.
-
C.
canTrackTargetsSimultaneously
Indicates the ability of an entity to follow or monitor multiple targets at the same time.
-
D.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
E.
usesSingleCamera
Indicates that an entity performs an action or operates in a context using only one camera rather than multiple cameras.
- 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_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 28, 2026, 6:16 a.m.