Triple
T30677272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24 Hours of Happy |
E780948
|
entity |
| Predicate | premieredAsWebsite |
P147588
|
FINISHED |
| Object | 24hoursofhappy.com |
—
|
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: 24hoursofhappy.com | Statement: [24 Hours of Happy, premieredAsWebsite, 24hoursofhappy.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premieredAsWebsite Context triple: [24 Hours of Happy, premieredAsWebsite, 24hoursofhappy.com]
-
A.
premieredOn
Indicates that an event, work, or production had its first public showing or debut on a specified date or at a specified time.
-
B.
premieredWith
Indicates that one entity made its first public debut or initial showing together with another entity, at the same time or in the same event.
-
C.
premieredAsVersionOf
Indicates that one work first appeared or was initially released as a particular version or variant of another work.
-
D.
premieredIn
Indicates that a creative work first publicly debuted or was initially presented in a particular place, event, or context.
-
E.
originalWebPremiere
chosen
Indicates that the subject had its first-ever release or debut specifically on the web or an online platform.
- 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_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 8:32 p.m.