Triple
T35806862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The American Badass |
E1035122
|
entity |
| Predicate | returnedForSpecialAppearance |
P48259
|
FINISHED |
| Object | WrestleMania 36 |
—
|
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: WrestleMania 36 | Statement: [The American Badass, returnedForSpecialAppearance, WrestleMania 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedForSpecialAppearance Context triple: [The American Badass, returnedForSpecialAppearance, WrestleMania 36]
-
A.
returnedFor
Indicates that an entity has been sent, given, or brought back in response to, or on behalf of, another entity or prior action.
-
B.
returnAppearance
Indicates that one entity resumes or restores a previous visual form, style, or outward appearance of another entity or of itself.
-
C.
returnsInSpecial
Indicates that an entity returns to a designated special location, state, or context rather than a standard or default one.
-
D.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
E.
specialAppearance
chosen
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:06 p.m.