Triple
T35810138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Styles Clash |
E1035206
|
entity |
| Predicate | firstPromotionUsedIn |
P206066
|
FINISHED |
| Object | NJPW |
E314527
|
NE 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: NJPW | Statement: [Styles Clash, firstPromotionUsedIn, NJPW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPromotionUsedIn Context triple: [Styles Clash, firstPromotionUsedIn, NJPW]
-
A.
usedByPromotion
Indicates that something (such as a resource, item, or rule) is utilized or referenced as part of a specific promotion.
-
B.
usesPromotionFrom
Indicates that one entity applies or benefits from a promotion, discount, or marketing offer provided or originated by another entity.
-
C.
usesPromotion
Indicates that an entity applies or takes advantage of a specific promotion, discount, or special offer.
-
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.
introducedInPromotion
Indicates that an entity was first presented, launched, or made known as part of a specific promotional campaign or activity.
- F. None of above. chosen
Provenance (5 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4076d91da88190a12ed4914ae18f5c |
completed | June 28, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.