Triple
T35805429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | BatistaRecordInTrilogy |
P168961
|
FINISHED |
| Object | 3–0 vs Triple H in 2005 PPV title matches |
—
|
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: 3–0 vs Triple H in 2005 PPV title matches | Statement: [Batista vs Triple H, BatistaRecordInTrilogy, 3–0 vs Triple H in 2005 PPV title matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BatistaRecordInTrilogy Context triple: [Batista vs Triple H, BatistaRecordInTrilogy, 3–0 vs Triple H in 2005 PPV title matches]
-
A.
WWFHardcoreChampion
Indicates that an entity holds or has held the WWF Hardcore Championship title in professional wrestling.
-
B.
batName
Indicates that a bat is identified by or associated with a specific name.
-
C.
أشهر الألقاب
Indicates that one or more entities are the most famous or widely known by certain nicknames or titles.
-
D.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
E.
bearerRivalOf
chosen
Indicates that the bearer is in a state of rivalry or competitive opposition with the related 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.