Triple
T33415965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorry for Your Loss |
E855716
|
entity |
| Predicate | hasOnlinePremiere |
P147588
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sorry for Your Loss, hasOnlinePremiere, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlinePremiere Context triple: [Sorry for Your Loss, hasOnlinePremiere, true]
-
A.
originalWebPremiere
chosen
Indicates that the subject had its first-ever release or debut specifically on the web or an online platform.
-
B.
premieredOn
Indicates that an event, work, or production had its first public showing or debut on a specified date or at a specified time.
-
C.
premiereOnPlatform
Indicates that a creative work has its first public release or debut on a specific distribution platform.
-
D.
worldPremiereDate
Indicates the date on which a work (such as a film, play, or musical piece) is first publicly premiered anywhere in the world.
-
E.
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.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1:36 a.m.