Triple
T26346568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Hardcore Championship |
E662789
|
entity |
| Predicate | ruleEnforcement |
P18859
|
FINISHED |
| Object | falls could occur outside the arena |
—
|
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: falls could occur outside the arena | Statement: [WWE Hardcore Championship, ruleEnforcement, falls could occur outside the arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleEnforcement Context triple: [WWE Hardcore Championship, ruleEnforcement, falls could occur outside the arena]
-
A.
enablesEnforcementOf
Indicates that one entity provides the authority, means, or conditions necessary for another entity to carry out enforcement actions or apply rules.
-
B.
decisionEnforcement
Indicates that an authority or mechanism compels compliance with, or carries out, a previously made decision or ruling.
-
C.
enforcesRule
Indicates that one entity compels or ensures that another entity follows or complies with a specified rule or set of rules.
-
D.
enforcement
chosen
Indicates the act of compelling compliance with rules, laws, or agreements through monitoring, pressure, or sanctions.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa7f0588190988ce7483ab7523d |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:42 p.m.