Triple

T35900651
Position Surface form Disambiguated ID Type / Status
Subject Booze, Broads & Bullets E1038342 entity
Predicate featuresCharacter P626 FINISHED
Object Fat Man
Fat Man is a recurring character in the Sin City graphic novel series, known as one of the grotesque, darkly comic figures populating Frank Miller’s violent noir world.
E2160565 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: Fat Man | Statement: [Booze, Broads & Bullets, featuresCharacter, Fat Man]
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: Fat Man
Triple: [Booze, Broads & Bullets, featuresCharacter, Fat Man]
Generated description
Fat Man is a recurring character in the Sin City graphic novel series, known as one of the grotesque, darkly comic figures populating Frank Miller’s violent noir world.

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_69f76e2190f88190beb2eed798a4ef01 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7aa699d68819081ed363931894ab3 completed May 3, 2026, 8:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38a503d23081908e7a3ed605f13c7c completed June 22, 2026, 2:59 a.m.
NEDg Description generation batch_6a38a5abc604819084de021a2c2262a3 completed June 22, 2026, 3:02 a.m.
NED2 Entity disambiguation (via description) batch_6a38a63caecc8190a4ac4eb8af4bb18b completed June 22, 2026, 3:04 a.m.
Created at: May 3, 2026, 4:07 p.m.