Triple
T35636425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunther vs. Sheamus vs. Drew McIntyre |
E1029731
|
entity |
| Predicate | championEntrance |
P109608
|
FINISHED |
| Object | Gunther |
—
|
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: Gunther | Statement: [Gunther vs. Sheamus vs. Drew McIntyre, championEntrance, Gunther]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championEntrance Context triple: [Gunther vs. Sheamus vs. Drew McIntyre, championEntrance, Gunther]
-
A.
championEnteringBout
Indicates that an entity who holds a championship title is entering or participating in a competitive bout or match.
-
B.
challengerEnteringRing
Indicates that a challenger is in the process of entering a competitive ring or arena to participate in a contest or match.
-
C.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
D.
champion
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
E.
heavyweightChampionEnteringEvent
chosen
Indicates that a heavyweight champion is entering or participating in a particular event.
- 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_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.