Triple
T16879246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Believe the Hype |
E421374
|
entity |
| Predicate | hasChantOrHook |
P69675
|
FINISHED |
| Object | "Don't believe the hype" |
—
|
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: "Don't believe the hype" | Statement: [Don't Believe the Hype, hasChantOrHook, "Don't believe the hype"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChantOrHook Context triple: [Don't Believe the Hype, hasChantOrHook, "Don't believe the hype"]
-
A.
hasChorusHook
Indicates that a musical work features a prominent, recurring chorus section that serves as a memorable hook.
-
B.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
C.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
-
D.
hasChantStyleHook
chosen
Indicates that something possesses or is associated with a specific chant-style hook as a characteristic or feature.
-
E.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f9aea0819090aef3c0c1ad349d |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.