Triple
T35600303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NJPW Strong |
E1028746
|
entity |
| Predicate | basedOnPromotion |
P199301
|
FINISHED |
| Object | New Japan Pro-Wrestling |
—
|
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: New Japan Pro-Wrestling | Statement: [NJPW Strong, basedOnPromotion, New Japan Pro-Wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnPromotion Context triple: [NJPW Strong, basedOnPromotion, New Japan Pro-Wrestling]
-
A.
usedByPromotion
Indicates that something (such as a resource, item, or rule) is utilized or referenced as part of a specific promotion.
-
B.
usesPromotion
Indicates that an entity applies or takes advantage of a specific promotion, discount, or special offer.
-
C.
usesPromotionFrom
Indicates that one entity applies or benefits from a promotion, discount, or marketing offer provided or originated by another entity.
-
D.
associatedWithPromotion
Indicates a relationship in which an entity is connected to, involved in, or affected by a specific promotion or promotional activity.
-
E.
hasPromotionTarget
Indicates that an entity is the intended recipient, audience, or focus of a promotional activity or campaign.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
| PDg | Predicate description generation | batch_69ff2d21f0a48190ad2ef5901cb07d93 |
completed | May 9, 2026, 12:48 p.m. |
Created at: May 3, 2026, 4:05 p.m.