Triple
T24203283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Elite Wrestling |
E600034
|
entity |
| Predicate | hasNotableWrestler |
P49139
|
FINISHED |
| Object | Chris Jericho |
—
|
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: Chris Jericho | Statement: [All Elite Wrestling, hasNotableWrestler, Chris Jericho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableWrestler Context triple: [All Elite Wrestling, hasNotableWrestler, Chris Jericho]
-
A.
hasNotableBoxer
Indicates that an entity is associated with or characterized by a boxer who is considered notable or distinguished.
-
B.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
-
C.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
D.
featuredWrestler
chosen
Indicates that a particular wrestler is highlighted or prominently showcased in a given context or event.
-
E.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
- 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.