Triple
T33069155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blues for Fred |
E846184
|
entity |
| Predicate | composerOfRepertoire |
P193372
|
FINISHED |
| Object | Cole Porter |
—
|
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: Cole Porter | Statement: [Blues for Fred, composerOfRepertoire, Cole Porter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerOfRepertoire Context triple: [Blues for Fred, composerOfRepertoire, Cole Porter]
-
A.
catalogueOfComposer
Indicates that one entity is a catalogue that systematically lists or documents the works of a particular composer.
-
B.
composerOfCataloguedWork
Indicates that one entity is the composer or creator of a specific catalogued musical or artistic work associated with another entity.
-
C.
dedicatedComposerOfVariations
Indicates that one entity is the composer specifically responsible for creating a set of musical variations associated with another entity.
-
D.
notableComposerOfType
Indicates that an entity is a well-known or distinguished composer associated with a specified type, category, or genre of composition.
-
E.
publishedComposer
Indicates that a composer has had their musical works formally published, typically by a recognized publisher or label.
- F. None of above. chosen
Provenance (4 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: May 1, 2026, 1:25 a.m.