Triple
T37469471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inhuman Rampage |
E931116
|
entity |
| Predicate | includesTrack |
P3284
|
FINISHED |
| Object |
The Flame of Youth
"The Flame of Youth" is a high-energy power metal song by British band DragonForce, featured on their 2006 album *Inhuman Rampage*.
|
E2229517
|
NE 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 Flame of Youth | Statement: [Inhuman Rampage, includesTrack, The Flame of Youth]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: The Flame of Youth Triple: [Inhuman Rampage, includesTrack, The Flame of Youth]
Generated description
"The Flame of Youth" is a high-energy power metal song by British band DragonForce, featured on their 2006 album *Inhuman Rampage*.
Provenance (5 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e3c8e248190b4a4067b9262c845 |
completed | May 6, 2026, 6:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a408c36f614819086bf8c014d9f6f5c |
completed | June 28, 2026, 2:51 a.m. |
| NEDg | Description generation | batch_6a408de6d5208190ab2224b2fbdb1ee5 |
completed | June 28, 2026, 2:58 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a408ecbdde0819096614ac9298e3de8 |
completed | June 28, 2026, 3:02 a.m. |
Created at: May 3, 2026, 4:17 p.m.