Triple
T30774029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikon Z 8 |
E783608
|
entity |
| Predicate | videoCodecs |
P169203
|
FINISHED |
| Object | ProRes 422 HQ |
—
|
NE NERFINISHED |
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: ProRes 422 HQ | Statement: [Nikon Z 8, videoCodecs, ProRes 422 HQ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoCodecs Context triple: [Nikon Z 8, videoCodecs, ProRes 422 HQ]
-
A.
videoEncoding
Indicates that one entity is used to encode, compress, or transform video data into a particular digital format or representation for another entity.
-
B.
rawVideoFormats
Indicates that an entity supports or is associated with one or more uncompressed or minimally processed (raw) video file formats.
-
C.
supportsHEVCEncode
Indicates that one entity provides the capability for another entity to perform HEVC (High Efficiency Video Coding) encoding.
-
D.
relatedCodec
chosen
Indicates that one entity is associated with or corresponds to another through a shared or compatible codec used for encoding or decoding data.
-
E.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:40 p.m.