Triple
T35806181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shane McMahon |
E1035105
|
entity |
| Predicate | performedStunt |
P96883
|
FINISHED |
| Object | high dives from the TitanTron |
—
|
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 dives from the TitanTron | Statement: [Shane McMahon, performedStunt, high dives from the TitanTron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedStunt Context triple: [Shane McMahon, performedStunt, high dives from the TitanTron]
-
A.
performedTrick
chosen
Indicates that one entity executed or carried out a trick involving another entity or in a particular context.
-
B.
hasStunts
Indicates that one entity performs, includes, or is associated with stunt actions for another entity or context.
-
C.
stuntPerformerIn
Indicates that one entity serves as a stunt performer in a work, production, or performance associated with another entity.
-
D.
leadActorPerformedOwnStunts
Indicates that the lead actor personally carried out the stunts in the production rather than using a stunt double.
-
E.
hasPublicityStunt
Indicates that an entity engages in or is associated with a planned publicity stunt intended to attract public attention.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 3, 2026, 4:06 p.m.