Triple
T23829913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonard Feather |
E589483
|
entity |
| Predicate | wroteLinerNotesFor |
P62982
|
FINISHED |
| Object | various jazz albums |
—
|
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: various jazz albums | Statement: [Leonard Feather, wroteLinerNotesFor, various jazz albums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteLinerNotesFor Context triple: [Leonard Feather, wroteLinerNotesFor, various jazz albums]
-
A.
hasLinerNotesWrittenBy
chosen
Indicates that the liner notes of an item (such as an album or release) are authored by a specified agent.
-
B.
notableAlbumContribution
Indicates that an entity made a significant creative or performance contribution to a particular music album.
-
C.
notableSongWrittenFor
Indicates that a particular song was specifically written for a given person, group, work, event, or purpose.
-
D.
authorOfAfterwordOrNotes
Indicates that one entity is the author of an afterword or explanatory notes accompanying another entity (such as a work or edition).
-
E.
writtenForPerformer
Indicates that a work was specifically composed or created to be performed by a particular performer or type of performer.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f498c48190827e59df868c5cb1 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:01 p.m.