Triple
T30266147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 (Oasis) |
E769650
|
entity |
| Predicate | hasBandMemberDeparture |
P79946
|
FINISHED |
| Object | Paul "Bonehead" Arthurs |
—
|
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: Paul "Bonehead" Arthurs | Statement: [1999 (Oasis), hasBandMemberDeparture, Paul "Bonehead" Arthurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBandMemberDeparture Context triple: [1999 (Oasis), hasBandMemberDeparture, Paul "Bonehead" Arthurs]
-
A.
associatedWithBandMemberDeparture
chosen
Indicates that an event, action, or circumstance is connected to or results from a band member leaving the band.
-
B.
hasBandMember
Indicates that a musical group includes a specific individual as one of its members.
-
C.
dateOfLeavingBand
Indicates the specific date on which a person stopped being a member of a particular band.
-
D.
hasFormerKeyboardist
Indicates that an entity previously had another entity serving as its keyboardist, but that person is no longer in that role.
-
E.
formerBandMembership
Indicates that an entity previously belonged to a musical group or band but is no longer a member.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 7:43 p.m.