Triple
T38619585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackmagic URSA Broadcast G2 |
E936831
|
entity |
| Predicate | supportsRemoteControl |
P167507
|
FINISHED |
| Object | SDI camera control |
—
|
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: SDI camera control | Statement: [Blackmagic URSA Broadcast G2, supportsRemoteControl, SDI camera control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRemoteControl Context triple: [Blackmagic URSA Broadcast G2, supportsRemoteControl, SDI camera control]
-
A.
supportsRemotePlay
Indicates that one entity enables or is compatible with remote play functionality for another entity.
-
B.
isRemoteControlled
chosen
Indicates that an entity is operated or controlled from a distance via a remote device or system.
-
C.
supportsRemoteTerminal
Indicates that one entity provides or enables access to another entity via a remote terminal interface.
-
D.
supportsSoftwareControl
Indicates that one entity enables or is compatible with the management, operation, or regulation of another entity through software-based control mechanisms.
-
E.
supportsImmediateControl
Indicates that one entity enables or allows another entity to exercise direct, real-time control over it without intermediate steps or delays.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.