Triple
T37106131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perchik |
E918845
|
entity |
| Predicate | lyricistAssociatedWork |
P111764
|
FINISHED |
| Object | Sheldon Harnick |
—
|
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: Sheldon Harnick | Statement: [Perchik, lyricistAssociatedWork, Sheldon Harnick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricistAssociatedWork Context triple: [Perchik, lyricistAssociatedWork, Sheldon Harnick]
-
A.
lyricist
Indicates that one entity is the writer of the words (lyrics) for a musical work associated with another entity.
-
B.
hasWrittenLyricsFor
chosen
Indicates that one entity is the lyricist who has created the words for a song or musical work performed or associated with another entity.
-
C.
lyricallyPairedWith
Indicates that two musical or poetic elements are intentionally matched or combined in lyrics, such as being written to accompany each other or to form a complementary lyrical pair.
-
D.
writerOfMusicAndLyrics
Indicates that a person is the creator of both the musical composition and the song lyrics for a work.
-
E.
lyricsBy
Indicates that the lyrics of a song or musical work were written or authored by a specified person or entity.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.