Triple
T37599118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackmagic URSA Mini Pro |
E935474
|
entity |
| Predicate | hasMonitoringFeature |
P200677
|
FINISHED |
| Object | focus peaking |
—
|
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: focus peaking | Statement: [Blackmagic URSA Mini Pro, hasMonitoringFeature, focus peaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonitoringFeature Context triple: [Blackmagic URSA Mini Pro, hasMonitoringFeature, focus peaking]
-
A.
canBeMonitoredWith
Indicates that one entity is suitable or able to be observed, tracked, or supervised using another specified entity or method.
-
B.
isMonitored
Indicates that an entity is being actively observed, tracked, or supervised by another entity or system.
-
C.
hasSatelliteMonitoring
Indicates that an entity is being observed or tracked using satellite-based monitoring systems.
-
D.
supportsRealTimeMonitoring
Indicates that an entity provides the capability to observe and track relevant data or events continuously as they occur in real time.
-
E.
hasEmergencyFeature
Indicates that an entity includes or supports a special function or capability intended for use in emergency situations.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.