Triple
T25899411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erin Burkett |
E652562
|
entity |
| Predicate | roleAtFatWreckChords |
P159838
|
FINISHED |
| Object | artist relations |
—
|
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: artist relations | Statement: [Erin Burkett, roleAtFatWreckChords, artist relations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtFatWreckChords Context triple: [Erin Burkett, roleAtFatWreckChords, artist relations]
-
A.
roleAtFatWreckChords
chosen
Indicates that an entity holds or held a specific role or position at Fat Wreck Chords.
-
B.
hasNotableGuitarRiffBy
Indicates that something (typically a song or musical piece) is characterized by a notable guitar riff performed or created by a specified guitarist.
-
C.
hasRhythmGuitar
Indicates that an entity includes or features a rhythm guitar as part of its musical instrumentation or arrangement.
-
D.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
E.
workRoleInRocknRolla
Indicates the specific role or function an entity has within the context of the work "RocknRolla."
- 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 8:23 a.m.