Triple
T5454293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VistaVision |
E122441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-resolution film format |
C2665
|
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: high-resolution film format Context triple: [VistaVision, instanceOf, high-resolution film format]
-
A.
high-definition video format
A high-definition video format is a digital video standard that delivers significantly higher resolution, clarity, and detail than standard-definition formats, typically including 720p, 1080p, or higher resolutions.
-
B.
large-format motion picture film system
chosen
A large-format motion picture film system is a high-resolution cinematic technology that uses wider or taller film stock and specialized cameras and projectors to capture and display images with greater detail, clarity, and immersive scale than standard film formats.
-
C.
film exhibition format
A film exhibition format is a standardized method or medium (such as 35mm, IMAX, or digital projection) used to present motion pictures to an audience in theaters or other viewing environments.
-
D.
high-dynamic-range imaging technology
High-dynamic-range imaging technology is a method of capturing, processing, and displaying images with a wider range of luminance and color than standard imaging, preserving detail in both very bright and very dark areas.
-
E.
motion picture camera
A motion picture camera is a device that captures a sequence of images on film or digital media at a consistent frame rate to create the illusion of moving pictures.
- F. None of above.
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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:08 p.m.