Triple
T11830621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 808 PureView |
E281379
|
entity |
| Predicate | videoFrameRate |
P68881
|
FINISHED |
| Object | 30 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: 30 fps | Statement: [Nokia 808 PureView, videoFrameRate, 30 fps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoFrameRate Context triple: [Nokia 808 PureView, videoFrameRate, 30 fps]
-
A.
originalFrameRate
Indicates the frame rate at which the original media content was captured or encoded before any conversion or processing.
-
B.
propertyType_maxFramerate
chosen
Indicates the maximum frame rate value that the property can support or is configured to allow.
-
C.
supportsFrameRates
Indicates that one entity is capable of operating with, handling, or being compatible with the specified frame rates of another entity.
-
D.
videoQuality
Indicates the level or standard of clarity, resolution, and overall visual fidelity associated with a given video.
-
E.
pegRate
Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62b75dc8190b27d24e46a262a11 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.