Triple
T38333927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WrestleMania XX |
E1037899
|
entity |
| Predicate | specialGuestReferee |
P194227
|
FINISHED |
| Object | Steve Austin |
—
|
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: Steve Austin | Statement: [WrestleMania XX, specialGuestReferee, Steve Austin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialGuestReferee Context triple: [WrestleMania XX, specialGuestReferee, Steve Austin]
-
A.
mainEventSpecialReferee
Indicates that a special referee is assigned to officiate the main event in a competition or show.
-
B.
BattleOfTheBillionairesSpecialReferee
Indicates that an entity serves as the special referee in the "Battle of the Billionaires" event or match.
-
C.
conferenceOfChampion
Indicates a relationship where a conference or event is held to recognize, feature, or determine a champion.
-
D.
refereeFrom
Indicates that an individual serving as a referee originates from or is associated with a particular place or organization.
-
E.
featuredMatchStipulation
Indicates that a particular rule, condition, or special stipulation is prominently associated with a highlighted or main match.
- F. None of above. chosen
Provenance (4 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_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: May 3, 2026, 4:30 p.m.