Triple
T37479968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackmagic Pocket Cinema Camera 4K |
E931387
|
entity |
| Predicate | maxFrameRateAtHD |
P68881
|
FINISHED |
| Object | 120 fps |
—
|
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: 120 fps | Statement: [Blackmagic Pocket Cinema Camera 4K, maxFrameRateAtHD, 120 fps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxFrameRateAtHD Context triple: [Blackmagic Pocket Cinema Camera 4K, maxFrameRateAtHD, 120 fps]
-
A.
propertyType_maxFramerate
chosen
Indicates the maximum frame rate value that the property can support or is configured to allow.
-
B.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
C.
hasMaxMacroblocksPerSecond
Indicates the maximum number of macroblocks that can be processed or handled per second in a given context.
-
D.
commonFrameRate
Indicates that two or more media items share the same frame rate.
-
E.
supportsFrameRates
Indicates that one entity is capable of operating with, handling, or being compatible with the specified frame rates of 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.