Triple

T18351476
Position Surface form Disambiguated ID Type / Status
Subject Killing Commendatore E439675 entity
Predicate hasCharacter P2308 FINISHED
Object Tomohiko Amada
Tomohiko Amada is a reclusive, elderly Japanese painter whose mysterious past and artwork play a central role in Haruki Murakami’s novel "Killing Commendatore."
E2291410 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: Tomohiko Amada | Statement: [Killing Commendatore, hasCharacter, Tomohiko Amada]
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: Tomohiko Amada
Triple: [Killing Commendatore, hasCharacter, Tomohiko Amada]
Generated description
Tomohiko Amada is a reclusive, elderly Japanese painter whose mysterious past and artwork play a central role in Haruki Murakami’s novel "Killing Commendatore."

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_69d8b918221c8190a9f7b563d64ac677 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e514f83b648190b473cf611851c666 completed April 19, 2026, 5:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5c5a16c3d081909e7e037099c1852d completed July 19, 2026, 5:01 a.m.
NEDg Description generation batch_6a5c5bc7e94081909a01c163478fe41c completed July 19, 2026, 5:08 a.m.
NED2 Entity disambiguation (via description) batch_6a5c5c20b2e48190a11b58114e05aa07 completed July 19, 2026, 5:09 a.m.
Created at: April 10, 2026, 10:37 a.m.