Triple
T5454329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VistaVision |
E122441
|
entity |
| Predicate | projectionMethod |
P30533
|
FINISHED |
| Object | non-anamorphic |
—
|
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: non-anamorphic | Statement: [VistaVision, projectionMethod, non-anamorphic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectionMethod Context triple: [VistaVision, projectionMethod, non-anamorphic]
-
A.
projectionFormat
chosen
Indicates the specific technical format or method used to project visual content (such as film or digital media) onto a display surface.
-
B.
projectionEffect
Indicates the visual or spatial transformation produced when something is projected from one surface, medium, or viewpoint onto another.
-
C.
reconstructionMethod
Indicates the technique or process used to reconstruct, restore, or rebuild something from its original or fragmented state.
-
D.
realizationMethod
Indicates the means, process, or technique by which something is carried out, implemented, or brought into effect.
-
E.
beamApprox
Indicates that one entity is approximately equal to or closely resembles another in value, form, or behavior.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.