Triple
T3088619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana Jones Epic Stunt Spectacular! |
E64432
|
entity |
| Predicate | hasStunts |
P45832
|
FINISHED |
| Object | high falls |
—
|
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: high falls | Statement: [Indiana Jones Epic Stunt Spectacular!, hasStunts, high falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStunts Context triple: [Indiana Jones Epic Stunt Spectacular!, hasStunts, high falls]
-
A.
hasStuntDouble
Indicates that one entity serves as a stunt double who performs dangerous or physically demanding actions on behalf of another entity.
-
B.
hasExtraordinaryExercise
Indicates that an entity engages in an unusually intense, prolonged, or otherwise exceptional level of physical exercise beyond typical norms.
-
C.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
D.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
E.
hasThrillRides
Indicates that an entity offers or includes thrill rides as part of its features or attractions.
- 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.