Triple
T30677301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Hours of Happy |
E780948
|
entity |
| Predicate | createdForCampaign |
P151240
|
FINISHED |
| Object | promotion of the single Happy |
—
|
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: promotion of the single Happy | Statement: [24 Hours of Happy, createdForCampaign, promotion of the single Happy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdForCampaign Context triple: [24 Hours of Happy, createdForCampaign, promotion of the single Happy]
-
A.
plannedCampaign
Indicates that an entity has designed and scheduled a campaign to be executed in the future.
-
B.
createdFor
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
C.
associatedWithCampaigns
chosen
Indicates that an entity has a connection or linkage to one or more campaigns, such as participation, inclusion, or relevance to those campaigns.
-
D.
createdByPromotion
Indicates that something came into existence or was produced as a direct result of a promotion or promotional activity.
-
E.
addsCampaign
Indicates that an entity creates or includes a campaign within a system or collection.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 29, 2026, 8:32 p.m.