Triple
T12200633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock or Bust World Tour |
E290699
|
entity |
| Predicate | reasonForDrummerReplacement |
P56544
|
FINISHED |
| Object | Phil Rudd legal issues |
—
|
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: Phil Rudd legal issues | Statement: [Rock or Bust World Tour, reasonForDrummerReplacement, Phil Rudd legal issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDrummerReplacement Context triple: [Rock or Bust World Tour, reasonForDrummerReplacement, Phil Rudd legal issues]
-
A.
previousDrummerReplaced
Indicates that one drummer took over the role from, and thus replaced, another drummer in a band or musical act.
-
B.
hasDrummer
Indicates that one entity serves as the drummer for, or plays drums in, another entity such as a band or musical group.
-
C.
replacedBecause
chosen
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
D.
replacedPlayer
Indicates that one player has been substituted out of play and replaced by another player.
-
E.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.