Triple
T14336284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CM Punk |
E355473
|
entity |
| Predicate | performedPipeBombPromoOn |
P113849
|
FINISHED |
| Object | 2011-06-27 |
—
|
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: 2011-06-27 | Statement: [CM Punk, performedPipeBombPromoOn, 2011-06-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedPipeBombPromoOn Context triple: [CM Punk, performedPipeBombPromoOn, 2011-06-27]
-
A.
usesPromotion
Indicates that an entity applies or takes advantage of a specific promotion, discount, or special offer.
-
B.
announcedPromotion
Indicates that an entity has publicly communicated the start or existence of a promotion or special offer to others.
-
C.
usesPromotionFrom
Indicates that one entity applies or benefits from a promotion, discount, or marketing offer provided or originated by another entity.
-
D.
hasPromotionFrom
Indicates that an entity receives or is associated with a promotion that originates from a specified source entity (such as a campaign, organization, or person).
-
E.
blewTrumpetIn
Indicates that an entity performed the action of blowing a trumpet in or at a specified location or context.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c2241e48190a0c626b3d741966a |
completed | April 14, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e8a40e4819080240c874da1842c |
completed | April 14, 2026, 12:09 p.m. |
Created at: April 10, 2026, 1:14 a.m.