Triple
T17365620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fate to Fatal |
E422181
|
entity |
| Predicate | notableVocalContribution |
P44280
|
FINISHED |
| Object | vocals by Kim Deal |
—
|
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: vocals by Kim Deal | Statement: [Fate to Fatal, notableVocalContribution, vocals by Kim Deal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVocalContribution Context triple: [Fate to Fatal, notableVocalContribution, vocals by Kim Deal]
-
A.
notableSongContributions
Indicates that an entity has made significant creative or performance contributions to one or more songs.
-
B.
vocalPerformanceNotedFor
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
C.
notableAlbumContribution
Indicates that an entity made a significant creative or performance contribution to a particular music album.
-
D.
hasVocalPerformanceBy
chosen
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
E.
notableChorus
Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a5016508190b0020471c9567065 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.