Triple
T24202951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jimmy Uso |
E600026
|
entity |
| Predicate | hasTagTeamFinisher |
P114135
|
FINISHED |
| Object | Double Uce |
—
|
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: Double Uce | Statement: [Jimmy Uso, hasTagTeamFinisher, Double Uce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTagTeamFinisher Context triple: [Jimmy Uso, hasTagTeamFinisher, Double Uce]
-
A.
wrestlingFinisher
chosen
Indicates that one entity is the signature or finishing wrestling move used by another entity.
-
B.
hasTagTeamDivision
Indicates that an entity participates in or is associated with a tag team division, typically involving teams of multiple members competing together.
-
C.
finalSmash
Indicates that one entity performs or activates a powerful, ultimate special attack or finishing move directed at another entity.
-
D.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
E.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
- 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_69f27ca2d6708190ba20d00870d0af49 |
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.