Triple
T34050821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breakaway |
E873217
|
entity |
| Predicate | hasSongwriterOnMultipleTracks |
P44022
|
FINISHED |
| Object | Stephen Bishop |
—
|
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: Stephen Bishop | Statement: [Breakaway, hasSongwriterOnMultipleTracks, Stephen Bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSongwriterOnMultipleTracks Context triple: [Breakaway, hasSongwriterOnMultipleTracks, Stephen Bishop]
-
A.
hasPrimarySongwriter
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with another entity.
-
B.
hasWrittenSongsFor
chosen
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
-
C.
hasSongwriterProducerRelationshipWith
Indicates a relationship where one entity serves as the songwriter and/or producer for another entity’s musical work.
-
D.
hasSongwriterOccupation
Indicates that an entity’s occupation or professional role is that of a songwriter.
-
E.
hasSingerSongwriter
Indicates that an entity is associated with a person who both sings and writes the songs for it.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 1:51 a.m.