Triple
T38333929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania XX |
E1037899
|
entity |
| Predicate | UndertakerCharacter |
P119159
|
FINISHED |
| Object | return of the Deadman persona |
—
|
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: return of the Deadman persona | Statement: [WrestleMania XX, UndertakerCharacter, return of the Deadman persona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UndertakerCharacter Context triple: [WrestleMania XX, UndertakerCharacter, return of the Deadman persona]
-
A.
bossCharacter
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
B.
eraCharacter
Indicates that a character is associated with, or belongs to, a particular historical or fictional era.
-
C.
worksUnderCharacter
Indicates that one character is hierarchically subordinate to another and performs their duties under that character’s authority or supervision.
-
D.
wrestlesUnderMask
Indicates that one entity participates in wrestling while concealing their identity with a mask.
-
E.
ultimatePersona
chosen
Indicates that one entity represents the final, most complete, or most authoritative persona or identity of 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:30 p.m.