Triple
T33853295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keith Gordon as Peter Miller |
E867692
|
entity |
| Predicate | workHasComposer |
P47024
|
FINISHED |
| Object | Pino Donaggio |
—
|
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: Pino Donaggio | Statement: [Keith Gordon as Peter Miller, workHasComposer, Pino Donaggio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workHasComposer Context triple: [Keith Gordon as Peter Miller, workHasComposer, Pino Donaggio]
-
A.
hasMusicalComposer
chosen
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
B.
producedComposer
Indicates that one entity served as the producer for a musical work created or composed by another entity.
-
C.
hasCoComposer
Indicates that an entity shares authorship of a musical composition with one or more other composers.
-
D.
workComposer
Indicates that one entity is the composer or creator of a musical or artistic work represented by the other entity.
-
E.
isRelatedWorkOfComposer
Indicates that one work is associated with or connected to a particular composer, typically as a composition created by that composer.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:47 a.m.