Triple
T31008951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujifilm X-T30 |
E790152
|
entity |
| Predicate | videoMaxFrameRateAt4K |
P68881
|
FINISHED |
| Object | 30p |
—
|
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: 30p | Statement: [Fujifilm X-T30, videoMaxFrameRateAt4K, 30p]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoMaxFrameRateAt4K Context triple: [Fujifilm X-T30, videoMaxFrameRateAt4K, 30p]
-
A.
supports4KVideoRecording
Indicates that the subject is capable of recording video at 4K (Ultra HD) resolution.
-
B.
propertyType_maxFramerate
chosen
Indicates the maximum frame rate value that the property can support or is configured to allow.
-
C.
4KRecommendedBandwidth
Indicates the amount of network bandwidth that is recommended to reliably stream or deliver 4K (ultra-high-definition) content.
-
D.
HDRVideo
Indicates that the video content is encoded or presented using High Dynamic Range, providing an expanded range of brightness and color compared to standard video.
-
E.
supportsProResVideo
Indicates that one entity provides the capability for another entity to record, process, or handle video in the ProRes format.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 29, 2026, 8:57 p.m.