Triple
T26346535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Hardcore Championship |
E662789
|
entity |
| Predicate | defenseRule |
P167283
|
FINISHED |
| Object | hardcore rules |
—
|
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: hardcore rules | Statement: [WWE Hardcore Championship, defenseRule, hardcore rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseRule Context triple: [WWE Hardcore Championship, defenseRule, hardcore rules]
-
A.
defenseStatus
Indicates the current state or condition of an entity’s defensive posture or protective readiness in a given context.
-
B.
defenseControl
Indicates that one entity exercises authority over, manages, or directs the defensive capabilities or protective measures of another entity.
-
C.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
D.
defenseLayer
Indicates a protective barrier or mechanism that shields an entity from harm, attack, or unwanted influence.
-
E.
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.
- 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_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 26, 2026, 10:42 p.m.