Triple
T30370119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interoperable Master Format |
E772524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | audiovisual packaging standard |
C56821
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: audiovisual packaging standard Context triple: [Interoperable Master Format, instanceOf, audiovisual packaging standard]
-
A.
audiovisual sector support programme
An audiovisual sector support programme is an initiative that provides financial, technical, and policy assistance to strengthen the creation, production, distribution, and promotion of film, television, and digital media content.
-
B.
audiovisual archive
An audiovisual archive is a curated collection of sound and moving image materials, preserved and organized for long-term access, research, and cultural memory.
-
C.
DIN standard
A DIN standard is a formal technical specification developed by the German Institute for Standardization (DIN) that defines uniform criteria, dimensions, methods, or quality requirements for products, processes, and services.
-
D.
VITA standard
A VITA standard is a set of open, consensus-based technical specifications developed by the VMEbus International Trade Association to define interoperable architectures, interfaces, and form factors for embedded computing systems.
-
E.
video compression standard
A video compression standard is a defined set of algorithms and rules that specify how digital video is encoded, transmitted, stored, and decoded to reduce file size while maintaining acceptable visual quality.
- F. None of above. chosen
Provenance (1 batch)
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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:59 p.m.