Triple
T29226450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High on Life |
E740945
|
entity |
| Predicate | isFestivalAnthem |
P36220
|
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: [High on Life, isFestivalAnthem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFestivalAnthem Context triple: [High on Life, isFestivalAnthem, true]
-
A.
isDefiningAnthemOf
Indicates that one entity serves as the official or primary anthem that represents or symbolizes another entity.
-
B.
isAnthemFor
chosen
Indicates that a song or musical composition serves as the official anthem representing a particular group, organization, place, or cause.
-
C.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
D.
isConsideredRockAnthem
Indicates that a song is widely regarded or recognized as a rock anthem, typically emblematic or iconic within the rock music genre.
-
E.
hasFestivalTheme
Indicates that something is associated with, characterized by, or designed around a particular festival-related theme.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664369428819085b3b0b647edd224 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:17 p.m.