Triple

T25278672
Position Surface form Disambiguated ID Type / Status
Subject Lovers Rock E633769 entity
Predicate hasTrack P3284 FINISHED
Object Somebody Already Broke My Heart
"Somebody Already Broke My Heart" is a smooth, melancholic soul track by Sade, noted for its understated groove and emotionally vulnerable lyrics.
E1670316 NE 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: Somebody Already Broke My Heart | Statement: [Lovers Rock, hasTrack, Somebody Already Broke My Heart]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Somebody Already Broke My Heart
Triple: [Lovers Rock, hasTrack, Somebody Already Broke My Heart]
Generated description
"Somebody Already Broke My Heart" is a smooth, melancholic soul track by Sade, noted for its understated groove and emotionally vulnerable lyrics.

Provenance (5 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_69e75a9402fc81909362ca85277c06d9 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f48e01001c8190b57c66866ec9f626 completed May 1, 2026, 11:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1067ff56508190b41b2421bfe52bce completed May 22, 2026, 2:28 p.m.
NEDg Description generation batch_6a1068aea8c88190b74dfa3f7386f860 completed May 22, 2026, 2:31 p.m.
NED2 Entity disambiguation (via description) batch_6a10694a8b4c81909a08075cbc76c9a9 completed May 22, 2026, 2:33 p.m.
Created at: April 21, 2026, 1:18 p.m.