Triple
T12295856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultra Panavision 70 |
E293083
|
entity |
| Predicate | usedInExhibitionFormat |
P12559
|
FINISHED |
| Object | 70 mm roadshow engagements |
—
|
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: 70 mm roadshow engagements | Statement: [Ultra Panavision 70, usedInExhibitionFormat, 70 mm roadshow engagements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInExhibitionFormat Context triple: [Ultra Panavision 70, usedInExhibitionFormat, 70 mm roadshow engagements]
-
A.
hasExhibitFormat
chosen
Indicates the specific format or medium in which an exhibit is presented or made available.
-
B.
exhibitionUse
Indicates that something is used, intended, or designated for display in an exhibition or exhibit context.
-
C.
exhibitedAs
Indicates that something is presented or displayed in a particular context, such as in a show, gallery, or exhibition.
-
D.
exhibitedWith
Indicates that two or more entities were presented or displayed together as part of the same exhibition or show.
-
E.
exhibitedBy
Indicates that something (such as a quality, behavior, or characteristic) is shown, displayed, or demonstrated by a particular entity.
- 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.