Triple
T25748898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Control (guest verse) |
E648415
|
entity |
| Predicate | producerOfSong |
P14044
|
FINISHED |
| Object | No I.D. |
—
|
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: No I.D. | Statement: [Control (guest verse), producerOfSong, No I.D.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producerOfSong Context triple: [Control (guest verse), producerOfSong, No I.D.]
-
A.
hasSongwriterProducerRelationshipWith
Indicates a relationship where one entity serves as the songwriter and/or producer for another entity’s musical work.
-
B.
producerArtist
chosen
Indicates that one entity serves as the producer (e.g., overseeing or managing the creation) of a work created or performed by the artist entity.
-
C.
sampledSongwriter
Indicates that one entity has used or incorporated a portion of another entity’s songwriting or composition as a sample in a new work.
-
D.
writerOfMusicAndLyrics
Indicates that a person is the creator of both the musical composition and the song lyrics for a work.
-
E.
keySongwriter
Indicates that the subject is the primary or main songwriter responsible for creating the song associated with the object.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 22, 2026, 4:32 a.m.