Triple
T35806368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Bottom |
E1035110
|
entity |
| Predicate | wrestlerLiftsOpponent |
P109976
|
FINISHED |
| Object | sideways |
—
|
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: sideways | Statement: [Rock Bottom, wrestlerLiftsOpponent, sideways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrestlerLiftsOpponent Context triple: [Rock Bottom, wrestlerLiftsOpponent, sideways]
-
A.
wrestlerInvolved
Indicates that a wrestler participates in or is directly involved in a particular wrestling-related event or action.
-
B.
positionInWrestling
chosen
Indicates the specific physical hold, stance, or arrangement of wrestlers relative to each other during a wrestling exchange or sequence.
-
C.
promotedWrestler
Indicates that one entity advanced, advertised, or otherwise publicly supported the wrestling career or appearances of another entity.
-
D.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
E.
managedWrestler
Indicates that one entity served as the manager of another entity in a professional wrestling context.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:06 p.m.