Triple
T12295836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultra Panavision 70 |
E293083
|
entity |
| Predicate | captureNegativeWidth |
P619
|
FINISHED |
| Object | 65 mm |
—
|
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: 65 mm | Statement: [Ultra Panavision 70, captureNegativeWidth, 65 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureNegativeWidth Context triple: [Ultra Panavision 70, captureNegativeWidth, 65 mm]
-
A.
negativeWidth
Indicates that the width of an entity or object is less than zero, representing an invalid or contradictory dimensional value.
-
B.
negativeAspectRatio
Indicates that the relationship or configuration between entities involves an aspect ratio value that is negative or otherwise invalid in sign.
-
C.
executionWidth
Indicates the degree of parallelism or number of concurrent units used when executing an operation or process.
-
D.
width
chosen
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
E.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:52 p.m.