Triple
T38619570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackmagic URSA Broadcast G2 |
E936831
|
entity |
| Predicate | hasRecordingMedia |
P196306
|
FINISHED |
| Object | CFast 2.0 |
—
|
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: CFast 2.0 | Statement: [Blackmagic URSA Broadcast G2, hasRecordingMedia, CFast 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingMedia Context triple: [Blackmagic URSA Broadcast G2, hasRecordingMedia, CFast 2.0]
-
A.
hasRecordingContract
Indicates that an entity is formally bound by an agreement to produce recordings for another entity, typically a record label or similar organization.
-
B.
hasVideoRecording
Indicates that there exists an associated video recording capturing or documenting the referenced entity or event.
-
C.
hasVideoRecordingAvailableOn
Indicates that a video recording of something is accessible or hosted on a specified platform, service, or medium.
-
D.
hasDigitalRecordingCapabilities
Indicates that an entity possesses the ability to create, store, or process information in digital recording form.
-
E.
recordingMedia
chosen
Indicates that one entity serves as the medium or format used to record, store, or capture information, signals, or content for another entity.
- 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.