Triple
T30350272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD DVD |
E771971
|
entity |
| Predicate | primaryVideoCodec |
P54493
|
FINISHED |
| Object | VC-1 |
E215061
|
NE 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: VC-1 | Statement: [HD DVD, primaryVideoCodec, VC-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVideoCodec Context triple: [HD DVD, primaryVideoCodec, VC-1]
-
A.
videoEncoding
chosen
Indicates that one entity is used to encode, compress, or transform video data into a particular digital format or representation for another entity.
-
B.
primaryStream
Indicates that one entity serves as the main or principal stream, channel, or flow associated with another entity, distinguishing it from secondary or auxiliary streams.
-
C.
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.
-
D.
supportsHEVCEncode
Indicates that one entity provides the capability for another entity to perform HEVC (High Efficiency Video Coding) encoding.
-
E.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
- F. None of above.
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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0207a1272c81909dcdb6e3307702f5 |
completed | May 11, 2026, 4:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a277c2b30008190bfe6c3ea7d68a44c |
completed | June 9, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_6a0205fa1e608190829fd2baa0434fff |
completed | May 11, 2026, 4:38 p.m. |
Created at: April 29, 2026, 7:56 p.m.