Triple

T30157103
Position Surface form Disambiguated ID Type / Status
Subject Three Hearts E766550 entity
Predicate hasPart P35 FINISHED
Object Heavy Hands (Acoustic)
"Heavy Hands (Acoustic)" is an acoustic rendition of the song "Heavy Hands," featured as a track on the release *Three Hearts*.
 E1901440 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: Heavy Hands (Acoustic) | Statement: [Three Hearts, hasPart, Heavy Hands (Acoustic)]
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: Heavy Hands (Acoustic)
Triple: [Three Hearts, hasPart, Heavy Hands (Acoustic)]
Generated description
"Heavy Hands (Acoustic)" is an acoustic rendition of the song "Heavy Hands," featured as a track on the release *Three Hearts*.

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_69f22479cd088190ab4c6f3fce39d1c5 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67ed7f408819091f6c5173b80cd38 completed May 2, 2026, 10:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a274cc58430819089c545e66291b310 completed June 8, 2026, 11:14 p.m.
NEDg Description generation batch_6a274d8dff508190b211a92328716611 completed June 8, 2026, 11:17 p.m.
NED2 Entity disambiguation (via description) batch_6a274e674bbc8190a88d0e74b663574a completed June 8, 2026, 11:21 p.m.
Created at: April 29, 2026, 7:21 p.m.