Triple
T35805438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | laterRevivalWinner |
P202419
|
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, laterRevivalWinner, Triple H]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRevivalWinner Context triple: [Batista vs Triple H, laterRevivalWinner, Triple H]
-
A.
revivalAnnouncedBy
Indicates that an entity’s revival (such as a show, event, or project being brought back) is publicly announced by a particular agent or source.
-
B.
revivalStars
Indicates a relationship where one entity initiates, leads, or is central to a revival, renewal, or comeback of another entity.
-
C.
revivalHost
Indicates that one entity serves as the host or venue where a revival event, such as a renewed performance, series, or movement, takes place.
-
D.
revivalVersionPerformer
Indicates that an entity performs or is responsible for a revival version of another entity (such as a work, production, or performance).
-
E.
revivalLeadActor
Indicates that the subject is the lead actor in a revival (new production or version) of the related work or performance.
- 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_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
| PDg | Predicate description generation | batch_6a007dd263b48190bd5de5386d45858b |
completed | May 10, 2026, 12:45 p.m. |
Created at: May 3, 2026, 4:06 p.m.