Triple
T30094423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Trousers |
E764823
|
entity |
| Predicate | hasComposerLyricist |
P46708
|
FINISHED |
| Object | William Finn |
—
|
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: William Finn | Statement: [In Trousers, hasComposerLyricist, William Finn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComposerLyricist Context triple: [In Trousers, hasComposerLyricist, William Finn]
-
A.
hasComposerLyricistTeam
Indicates a relationship where a musical work is associated with a specific team that jointly fulfills the roles of composer and lyricist.
-
B.
hasSongwriterProducerRelationshipWith
Indicates a relationship where one entity serves as the songwriter and/or producer for another entity’s musical work.
-
C.
hasSingerSongwriter
Indicates that an entity is associated with a person who both sings and writes the songs for it.
-
D.
writerOfMusicAndLyrics
chosen
Indicates that a person is the creator of both the musical composition and the song lyrics for a work.
-
E.
hasAdditionalSongwriter
Indicates that an entity (such as a song or musical work) credits one or more additional individuals as songwriters beyond the primary or originally listed songwriter(s).
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00cda99c908190980e0bf54cb2e2a4 |
completed | May 10, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a00cd1635b08190a791ecfcf87a1d54 |
completed | May 10, 2026, 6:23 p.m. |
Created at: April 29, 2026, 7:06 p.m.