Triple
T26346538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Hardcore Championship |
E662789
|
entity |
| Predicate | defenseStipulation |
P167746
|
FINISHED |
| Object | 24/7 rule |
—
|
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: 24/7 rule | Statement: [WWE Hardcore Championship, defenseStipulation, 24/7 rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseStipulation Context triple: [WWE Hardcore Championship, defenseStipulation, 24/7 rule]
-
A.
defenseAgreement
Indicates the existence of a formal or informal pact in which parties commit to support or protect each other in matters of defense or security.
-
B.
defenseArgument
Indicates that an entity presents or supports a line of reasoning intended to defend or justify another entity, often in a legal or argumentative context.
-
C.
defenseStatus
Indicates the current state or condition of an entity’s defensive posture or protective readiness in a given context.
-
D.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
-
E.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 26, 2026, 10:42 p.m.