Triple
T3088617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Jones Epic Stunt Spectacular! |
E64432
|
entity |
| Predicate | hasPyrotechnics |
P45831
|
FINISHED |
| Object | explosions |
—
|
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: explosions | Statement: [Indiana Jones Epic Stunt Spectacular!, hasPyrotechnics, explosions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPyrotechnics Context triple: [Indiana Jones Epic Stunt Spectacular!, hasPyrotechnics, explosions]
-
A.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
B.
usesPropellantType
Indicates that one entity operates or functions using a specific type of propellant as its fuel or reaction mass.
-
C.
explosiveDevice
Indicates the presence or involvement of an object designed to explode or cause an explosion in relation to the associated entities.
-
D.
hasVerticalLaunchSystem
Indicates that one entity is equipped with a vertical launch system used to fire missiles or similar munitions vertically.
-
E.
hasSpray
Indicates that one entity possesses, contains, or is equipped with a spray or spraying capability in relation to another entity or context.
- F. None of above. chosen
Provenance (4 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada20b99a4819090c3d3e08ed556ad |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.