Triple
T20713285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Orlando’s Horror Make-Up Show |
E509100
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special effects demonstration |
C3630
|
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: special effects demonstration Context triple: [Universal Orlando’s Horror Make-Up Show, instanceOf, special effects demonstration]
-
A.
special effects studio
A special effects studio is a creative production facility that designs, develops, and implements visual and practical effects for film, television, games, and other media to enhance or simulate on-screen realities.
-
B.
special effects studio
A special effects studio is a creative production facility that designs, develops, and executes visual and practical effects for film, television, games, and other media to enhance or transform on-screen imagery.
-
C.
visual effects equipment
Visual effects equipment comprises the specialized hardware and tools used to create, manipulate, and integrate visual elements—such as lighting, particles, motion capture, and compositing—into film, television, games, and other media productions.
-
D.
special effects supervisor
A special effects supervisor oversees the design, planning, and execution of practical and digital effects for film, television, or live productions to achieve the desired visual impact safely and convincingly.
-
E.
demonstration
chosen
A demonstration is a structured presentation or display of how something works, is performed, or can be used, typically to explain, prove, or showcase its features or effectiveness.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:15 p.m.