Triple
T37480145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rec. BT.2020 |
E931390
|
entity |
| Predicate | definesFrameRateRange |
P85775
|
FINISHED |
| Object | 24–120 Hz |
—
|
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: 24–120 Hz | Statement: [Rec. BT.2020, definesFrameRateRange, 24–120 Hz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesFrameRateRange Context triple: [Rec. BT.2020, definesFrameRateRange, 24–120 Hz]
-
A.
supportsFrameRates
chosen
Indicates that one entity is capable of operating with, handling, or being compatible with the specified frame rates of another entity.
-
B.
commonFrameRate
Indicates that two or more media items share the same frame rate.
-
C.
propertyType_maxFramerate
Indicates the maximum frame rate value that the property can support or is configured to allow.
-
D.
originalFrameRate
Indicates the frame rate at which the original media content was captured or encoded before any conversion or processing.
-
E.
frameDuration
Indicates the length of time that a single frame in a sequence (such as video or animation) is displayed before advancing to the next frame.
- 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_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:17 p.m.