Triple
T27879210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impact World Championship |
E705040
|
entity |
| Predicate | primaryDefenseEvents |
P200660
|
FINISHED |
| Object | Bound for Glory |
—
|
NE NERFINISHED |
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: Bound for Glory | Statement: [Impact World Championship, primaryDefenseEvents, Bound for Glory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDefenseEvents Context triple: [Impact World Championship, primaryDefenseEvents, Bound for Glory]
-
A.
featuresDefenseBy
Indicates that an entity possesses or is characterized by a defense mechanism, strategy, or protective feature provided or implemented by another entity.
-
B.
defenseTrigger
Indicates that one entity initiates or activates a defensive response or mechanism in another entity.
-
C.
defenseFunction
Indicates that an entity serves a protective or defensive role against threats, attacks, or harm to another entity or system.
-
D.
recognizesDefense
Indicates that one entity acknowledges, identifies, or accepts another entity’s defensive action, strategy, or legal defense as such.
-
E.
defenseIncludes
Indicates that a defense strategy, plan, or system contains or incorporates a particular component, measure, or element as part of it.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: April 27, 2026, 6:29 p.m.