Triple
T28196816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammer to Fall |
E716469
|
entity |
| Predicate | isFollowedByInSetlist |
P94024
|
FINISHED |
| Object | We Are the Champions |
—
|
NE NERFINISHED |
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: We Are the Champions | Statement: [Hammer to Fall, isFollowedByInSetlist, We Are the Champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFollowedByInSetlist Context triple: [Hammer to Fall, isFollowedByInSetlist, We Are the Champions]
-
A.
followsInTracklist
Indicates that one item directly comes after another in an ordered tracklist sequence.
-
B.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
-
C.
featuredInTourSetlistOf
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
D.
precedesSongInShow
chosen
Indicates that one song is performed or appears earlier than another song within the sequence of a show.
-
E.
hasSequelSong
Indicates that one song serves as a sequel or follow-up to another song, continuing or expanding its themes, story, or musical ideas.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642d23ea481908f010394a925b83f |
completed | May 2, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:28 p.m.