Triple
T28206041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie Fisher |
E717023
|
entity |
| Predicate | collaboratesOnSong |
P119373
|
FINISHED |
| Object | Way Back Into Love |
—
|
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: Way Back Into Love | Statement: [Sophie Fisher, collaboratesOnSong, Way Back Into Love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratesOnSong Context triple: [Sophie Fisher, collaboratesOnSong, Way Back Into Love]
-
A.
workedOnSong
Indicates that an entity contributed effort or participation to the creation, production, or performance of a particular song.
-
B.
workedOnSongFor
Indicates that one entity contributed work or effort toward creating, producing, or developing a particular song for another entity or purpose.
-
C.
creditedSongwritingPartnership
Indicates that two or more entities are formally acknowledged as co-writers of a song.
-
D.
wroteSongWith
chosen
Indicates that two or more entities collaborated in the creation or composition of a song.
-
E.
coveredSongBy
Indicates that one musical work is a cover version performed or recorded by an artist of a song originally created or popularized by another artist.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 10:35 p.m.