Triple
T24203379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anaconda Vise |
E600037
|
entity |
| Predicate | finishingMoveOf |
P80697
|
FINISHED |
| Object | CM Punk |
—
|
NE NERFINISHED |
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: CM Punk | Statement: [Anaconda Vise, finishingMoveOf, CM Punk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishingMoveOf Context triple: [Anaconda Vise, finishingMoveOf, CM Punk]
-
A.
hasFinishingMove
chosen
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.
formOfFinalMovement
Indicates that one movement serves as the concluding or final section of another movement or larger musical work.
-
D.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
E.
finalMovementKey
Indicates that one movement in a sequence is designated as the last or concluding movement, often used as a key or reference to the final step in a process or animation.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca38c148190ae65cd692567d43d |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.