Triple
T14659936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Issues |
E344209
|
entity |
| Predicate | previouslySongwriterFor |
P44022
|
FINISHED |
| Object | other artists |
—
|
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: other artists | Statement: [Issues, previouslySongwriterFor, other artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslySongwriterFor Context triple: [Issues, previouslySongwriterFor, other artists]
-
A.
hasWrittenSongsFor
chosen
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
-
B.
hasPrimarySongwriter
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with another entity.
-
C.
hasWrittenLyricsFor
Indicates that one entity is the lyricist who has created the words for a song or musical work performed or associated with another entity.
-
D.
songWrittenBy
Indicates that a particular song was created or composed by a specific person or group.
-
E.
writerOfMusicAndLyrics
Indicates that a person is the creator of both the musical composition and the song lyrics for a work.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51b6a248190a44050c0e0ec2d16 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.