Triple
T35805417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | rematchStipulation |
P48258
|
FINISHED |
| Object | World Heavyweight Championship singles match |
—
|
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: World Heavyweight Championship singles match | Statement: [Batista vs Triple H, rematchStipulation, World Heavyweight Championship singles match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rematchStipulation Context triple: [Batista vs Triple H, rematchStipulation, World Heavyweight Championship singles match]
-
A.
rematchPlanned
Indicates that a subsequent contest or match between the same parties has been scheduled or arranged.
-
B.
typicalMatchStipulation
Indicates that a condition or set of conditions is normally required or expected to be satisfied for a match or pairing between entities to be valid.
-
C.
featuredMatchStipulation
chosen
Indicates that a particular rule, condition, or special stipulation is prominently associated with a highlighted or main match.
-
D.
rematchDate
Indicates the date on which a subsequent or repeat contest between the same parties is scheduled or took place.
-
E.
rematchEvent
Indicates that an event is a subsequent contest or encounter held to replay or settle the outcome of a previous event between the same parties.
- 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_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.