Triple
T27981574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Daddy Splash |
E706637
|
entity |
| Predicate | associatedPromotion |
P103137
|
FINISHED |
| Object | Joint Promotions |
—
|
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: Joint Promotions | Statement: [Big Daddy Splash, associatedPromotion, Joint Promotions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPromotion Context triple: [Big Daddy Splash, associatedPromotion, Joint Promotions]
-
A.
associatedWithPromotion
chosen
Indicates a relationship in which an entity is connected to, involved in, or affected by a specific promotion or promotional activity.
-
B.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
C.
promotionFor
Indicates that one entity serves as a promotional activity, material, or campaign intended to advertise, support, or increase the visibility of another entity.
-
D.
promotionIn
Indicates that an entity is being advanced, elevated, or upgraded within a specified context, organization, or domain.
-
E.
includesPromotionFrom
Indicates that one entity contains or incorporates a promotion that originates from another entity.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
Created at: April 27, 2026, 7:44 p.m.