Triple
T35636424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunther vs. Sheamus vs. Drew McIntyre |
E1029731
|
entity |
| Predicate | wrestler3 |
P170068
|
FINISHED |
| Object | Drew McIntyre |
—
|
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: Drew McIntyre | Statement: [Gunther vs. Sheamus vs. Drew McIntyre, wrestler3, Drew McIntyre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrestler3 Context triple: [Gunther vs. Sheamus vs. Drew McIntyre, wrestler3, Drew McIntyre]
-
A.
managedWrestler
Indicates that one entity served as the manager of another entity in a professional wrestling context.
-
B.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
C.
featuredWrestler
Indicates that a particular wrestler is highlighted or prominently showcased in a given context or event.
-
D.
pinnedWrestler
Indicates that one wrestler has held another wrestler's shoulders to the mat in a position that could result in a pin or fall.
-
E.
wrestlerInvolved
chosen
Indicates that a wrestler participates in or is directly involved in a particular wrestling-related event or action.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:05 p.m.