Triple
T27846518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lance Cade |
E703835
|
entity |
| Predicate | usedFinishingMove |
P114135
|
FINISHED |
| Object | Sitout spinebuster |
—
|
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: Sitout spinebuster | Statement: [Lance Cade, usedFinishingMove, Sitout spinebuster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFinishingMove Context triple: [Lance Cade, usedFinishingMove, Sitout spinebuster]
-
A.
hasFinishingMove
Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
-
B.
finishMove
Indicates that an entity completes or brings to an end a movement or relocation action involving another entity or itself.
-
C.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
D.
formOfFinalMovement
Indicates that one movement serves as the concluding or final section of another movement or larger musical work.
-
E.
wrestlingFinisher
chosen
Indicates that one entity is the signature or finishing wrestling move used by 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 6:07 p.m.