Triple
T35805427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | notableStipulationType |
P113854
|
FINISHED |
| Object | Hell in a Cell |
E385132
|
NE 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: Hell in a Cell | Statement: [Batista vs Triple H, notableStipulationType, Hell in a Cell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStipulationType Context triple: [Batista vs Triple H, notableStipulationType, Hell in a Cell]
-
A.
notableStipulation
chosen
Indicates that there is a significant condition, requirement, or clause that meaningfully qualifies or constrains the related entity or relationship.
-
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.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
D.
notableRule
Indicates that a rule or regulation is particularly significant, prominent, or noteworthy within a given context.
-
E.
notableProvision
Indicates that one entity is a significant or noteworthy clause, term, or condition contained within another entity, such as a document, agreement, or law.
- F. None of above.
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_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389c1315ac8190b89c688207d92aba |
completed | June 22, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.