Triple
T24079388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radioactive |
E596462
|
entity |
| Predicate | labelMarketingTagline |
P95166
|
FINISHED |
| Object | the biggest rock hit of the year |
—
|
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: the biggest rock hit of the year | Statement: [Radioactive, labelMarketingTagline, the biggest rock hit of the year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelMarketingTagline Context triple: [Radioactive, labelMarketingTagline, the biggest rock hit of the year]
-
A.
labelMarketingPositioning
Indicates that an entity defines or assigns the marketing positioning (how something is presented or positioned in the market) for another entity.
-
B.
labelMarketingFocus
Indicates that something is designated as the primary marketing focus or emphasis within a given context.
-
C.
labelMarketingConcept
Indicates that something is designated or identified as a specific marketing concept.
-
D.
taglineForm
Indicates that one entity serves as the tagline or slogan associated with another entity.
-
E.
usedAsMarketingTaglineFor
chosen
Indicates that something is employed as a promotional slogan or catchphrase to market a particular product, service, brand, or entity.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db20ca648190bb168808623119da |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:43 p.m.