Triple
T3126104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addiction |
E65299
|
entity |
| Predicate | hasLyricistRole |
P1360
|
FINISHED |
| Object | primary lyricist |
—
|
LITERAL FINISHED |
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: primary lyricist | Statement: [Addiction, hasLyricistRole, primary lyricist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLyricistRole Context triple: [Addiction, hasLyricistRole, primary lyricist]
-
A.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
B.
lyricist
chosen
Indicates that one entity is the writer of the words (lyrics) for a musical work associated with another entity.
-
C.
hasComposerLyricistTeam
Indicates a relationship where a musical work is associated with a specific team that jointly fulfills the roles of composer and lyricist.
-
D.
hasPrimarySongwriter
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with another entity.
-
E.
coAuthorOfLibrettoWith
Indicates that two or more individuals collaborated in writing the same libretto.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada544cb648190b5ed430dbd561d52 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.