Triple
T22391764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killer Be Killed |
E553527
|
entity |
| Predicate | hasFormerMemberRole |
P1168
|
FINISHED |
| Object | Dave Elitch – drums |
—
|
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: Dave Elitch – drums | Statement: [Killer Be Killed, hasFormerMemberRole, Dave Elitch – drums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerMemberRole Context triple: [Killer Be Killed, hasFormerMemberRole, Dave Elitch – drums]
-
A.
hasNotableFormerMemberRole
Indicates that an entity has a role or position that was notably held by a former member of that entity.
-
B.
hasFormerStaffMember
Indicates that an entity once had a person as a staff member, but that person is no longer employed there.
-
C.
mayHavePriorRole
Indicates that an entity is allowed or expected to have held a specified role at some earlier time.
-
D.
performedByFormerGroupMemberOf
Indicates that an action or event is carried out by an individual who was previously a member of a specified group.
-
E.
formerMemberOf
chosen
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585b56208190b53b90a81a807a9d |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.