Triple
T9058242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanted Dead or Alive |
E217057
|
entity |
| Predicate | isDefiningAnthemOf |
P86139
|
FINISHED |
| Object | 1980s hard rock |
—
|
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: 1980s hard rock | Statement: [Wanted Dead or Alive, isDefiningAnthemOf, 1980s hard rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefiningAnthemOf Context triple: [Wanted Dead or Alive, isDefiningAnthemOf, 1980s hard rock]
-
A.
isAnthemFor
Indicates that a song or musical composition serves as the official anthem representing a particular group, organization, place, or cause.
-
B.
hasDistinctAnthemFor
Indicates that one entity has a unique, separate anthem specifically designated for the other entity.
-
C.
formallyConfirmedAsAnthemInYear
Indicates that something was officially recognized and confirmed as an anthem in a specific year.
-
D.
officialAnthem
Indicates that one entity serves as the formally designated anthem of another entity, such as a country, organization, or event.
-
E.
deFactoNationalAnthemOf
Indicates a song that, while not officially designated, is widely recognized and treated as the national anthem of a country or region.
- F. None of above. chosen
Provenance (4 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7ec808bc8190957b80820d98fd5b |
completed | April 1, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee6d83c819095d8ed0779aa8511 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:10 p.m.