Triple
T35809157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RKO (wrestling move) |
E1035180
|
entity |
| Predicate | signatureSetupGesture |
P15416
|
FINISHED |
| Object | Randy Orton pounding mat |
—
|
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: Randy Orton pounding mat | Statement: [RKO (wrestling move), signatureSetupGesture, Randy Orton pounding mat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureSetupGesture Context triple: [RKO (wrestling move), signatureSetupGesture, Randy Orton pounding mat]
-
A.
signatureGesture
chosen
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
B.
signatureManeuver
Indicates a distinctive or characteristic action or move that an entity is especially known for performing.
-
C.
signatureStep
Indicates that an action or process represents a distinct stage in completing or validating a signature.
-
D.
signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
-
E.
signatureFeature
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.