Triple
T13212703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IWGP Heavyweight Champion |
E314532
|
entity |
| Predicate | typicalDefenses |
P101803
|
FINISHED |
| Object | pay-per-view events |
—
|
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: pay-per-view events | Statement: [IWGP Heavyweight Champion, typicalDefenses, pay-per-view events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDefenses Context triple: [IWGP Heavyweight Champion, typicalDefenses, pay-per-view events]
-
A.
typicalDefenseFormat
chosen
Indicates the usual or standard defensive arrangement, structure, or strategy typically employed in a given context.
-
B.
recognizesDefense
Indicates that one entity acknowledges, identifies, or accepts another entity’s defensive action, strategy, or legal defense as such.
-
C.
defenseControl
Indicates that one entity exercises authority over, manages, or directs the defensive capabilities or protective measures of another entity.
-
D.
typeOfDefense
Indicates the specific kind or category of defense employed or possessed in a given context.
-
E.
defenseLayer
Indicates a protective barrier or mechanism that shields an entity from harm, attack, or unwanted influence.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9f0f148190a0698ef27573c885 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.