Triple
T30698612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony α7 IV |
E781547
|
entity |
| Predicate | videoOversampling |
P172530
|
FINISHED |
| Object | 7K oversampled to 4K at up to 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: 7K oversampled to 4K at up to 30p | Statement: [Sony α7 IV, videoOversampling, 7K oversampled to 4K at up to 30p]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoOversampling Context triple: [Sony α7 IV, videoOversampling, 7K oversampled to 4K at up to 30p]
-
A.
videoQuality
Indicates the level or standard of clarity, resolution, and overall visual fidelity associated with a given video.
-
B.
videoOutput
Indicates that one entity produces or provides video signals or content as output to another entity or medium.
-
C.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
-
D.
videoEncoding
Indicates that one entity is used to encode, compress, or transform video data into a particular digital format or representation for another entity.
-
E.
videoChip
Indicates a relationship where an entity functions as or contains a video-processing chip or component used for handling video signals or graphics.
- F. None of above. chosen
Provenance (4 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 29, 2026, 8:34 p.m.