Triple
T35809834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Game |
E1035198
|
entity |
| Predicate | associatedWithWrestlerRole |
P131400
|
FINISHED |
| Object | main eventer |
—
|
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: main eventer | Statement: [The Game, associatedWithWrestlerRole, main eventer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWrestlerRole Context triple: [The Game, associatedWithWrestlerRole, main eventer]
-
A.
associatedWrestler
Indicates that one entity is connected or linked to a particular wrestler, typically through participation, representation, or relevant involvement.
-
B.
wrestlingRole
chosen
Indicates the specific capacity or function an individual performs within a wrestling context, such as competitor, referee, coach, or other defined role.
-
C.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
D.
nicknameOfAssociatedWrestler
Indicates that one entity is a nickname that is used to refer to an associated professional wrestler.
-
E.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.