Triple
T35805423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | thirdMajorMatchLoser |
P192178
|
FINISHED |
| Object | Triple H |
—
|
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: Triple H | Statement: [Batista vs Triple H, thirdMajorMatchLoser, Triple H]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdMajorMatchLoser Context triple: [Batista vs Triple H, thirdMajorMatchLoser, Triple H]
-
A.
thirdMajorMatchWinner
Indicates that the subject is the winner of the third major match in a specified series or competition.
-
B.
featuredMatchLoser
Indicates that an entity is the participant who lost in a designated featured match.
-
C.
finalBoutLoser
Indicates that an entity is the competitor who lost in the final bout of a match, tournament, or competition.
-
D.
semifinalLoser
Indicates that an entity lost in a semifinal round of a competition or tournament.
-
E.
notablePlayerLosingTeam
Indicates that a particular player is a prominent or noteworthy member of the team that lost a given game or match.
- F. None of above. chosen
Provenance (4 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:06 p.m.