Triple
T15166483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upset The Rhythm |
E362358
|
entity |
| Predicate | promoterType |
P13067
|
FINISHED |
| Object | DIY promoter |
—
|
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: DIY promoter | Statement: [Upset The Rhythm, promoterType, DIY promoter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promoterType Context triple: [Upset The Rhythm, promoterType, DIY promoter]
-
A.
promotedWith
Indicates that one entity is advertised, marketed, or publicized together with another entity as part of the same promotional effort.
-
B.
promotesFrom
Indicates that one entity advances or elevates another entity from a lower position, role, or status to a higher one.
-
C.
promotionalRole
chosen
Indicates that an entity serves in a capacity focused on promoting, advertising, or publicizing another entity, product, or activity.
-
D.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
E.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064c6244819085daf8e1eafdf3f2 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.