Triple
T35805422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | thirdMajorMatchWinner |
P192093
|
FINISHED |
| Object | Batista |
—
|
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: Batista | Statement: [Batista vs Triple H, thirdMajorMatchWinner, Batista]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdMajorMatchWinner Context triple: [Batista vs Triple H, thirdMajorMatchWinner, Batista]
-
A.
featuredMatchWinner
Indicates that an entity is the winner of a highlighted or prominently featured match.
-
B.
masteryWonBy
Indicates that a particular mastery, title, or level of expertise is obtained or achieved by a specific entity.
-
C.
secondRoundWinner
Indicates that the subject is the winner of the second round in a multi-round competition, contest, or process.
-
D.
unificationMatchWinner
Indicates that an entity is the winner of a unification match between two or more competing entities.
-
E.
mainWinner
Indicates that one entity is the primary or overall winner in a competition, contest, or comparative outcome relative to others.
- 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_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.