Triple
T30454011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Weren’t Born to Follow |
E774801
|
entity |
| Predicate | hasAnthemicStyle |
P13181
|
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: [We Weren’t Born to Follow, hasAnthemicStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnthemicStyle Context triple: [We Weren’t Born to Follow, hasAnthemicStyle, true]
-
A.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
B.
hasChantingStyle
Indicates that an entity is associated with or characterized by a particular style or manner of chanting.
-
C.
hasSongStyle
chosen
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
-
D.
hasEnergeticVocals
Indicates that the subject performs vocals characterized by high energy, intensity, or liveliness.
-
E.
isConsideredRockAnthem
Indicates that a song is widely regarded or recognized as a rock anthem, typically emblematic or iconic within the rock music genre.
- 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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 8:09 p.m.