Triple
T22578565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blast |
E544494
|
entity |
| Predicate | hasAudienceResponse |
P148801
|
FINISHED |
| Object | high emotional impact |
—
|
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: high emotional impact | Statement: [The Blast, hasAudienceResponse, high emotional impact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceResponse Context triple: [The Blast, hasAudienceResponse, high emotional impact]
-
A.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
hasAudienceFormat
Indicates that an entity is associated with a particular format or medium in which its audience receives or experiences it.
-
C.
hasAudienceOrigin
Indicates that an audience is characterized by or associated with a particular geographic, cultural, or demographic origin.
-
D.
hasAudiencePolicy
Indicates that there is a specified rule or policy governing which audience or group is allowed to access, view, or receive something.
-
E.
hasAudienceExpectation
Indicates that one entity holds assumptions or anticipates certain reactions, knowledge, or behavior from its audience in relation to another entity or context.
- F. None of above. chosen
Provenance (4 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15feee27c8190b31c923e1f00a363 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 8:53 p.m.