Triple
T27879858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abyss |
E705055
|
entity |
| Predicate | postWrestlingRole |
P131400
|
FINISHED |
| Object | producer in WWE |
—
|
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: producer in WWE | Statement: [Abyss, postWrestlingRole, producer in WWE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postWrestlingRole Context triple: [Abyss, postWrestlingRole, producer in WWE]
-
A.
wrestlingRole
chosen
Indicates the specific capacity or function an individual performs within a wrestling context, such as competitor, referee, coach, or other defined role.
-
B.
postPlayingRole
Indicates that an entity assumes or holds a particular role after a playing or performance event has taken place.
-
C.
managedWrestler
Indicates that one entity served as the manager of another entity in a professional wrestling context.
-
D.
roleInGigantomachy
Indicates the specific part or function an entity played in the mythological conflict known as the Gigantomachy.
-
E.
promotedWrestler
Indicates that one entity advanced, advertised, or otherwise publicly supported the wrestling career or appearances 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:29 p.m.