Triple

T29651267
Position Surface form Disambiguated ID Type / Status
Subject Hin Bredendieck E750138 entity
Predicate givenName P17 FINISHED
Object Hin
Hin is a given name most notably associated with Hin Bredendieck, a German-American industrial designer linked to the Bauhaus movement.
E1876276 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: Hin | Statement: [Hin Bredendieck, givenName, Hin]
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: Hin
Triple: [Hin Bredendieck, givenName, Hin]
Generated description
Hin is a given name most notably associated with Hin Bredendieck, a German-American industrial designer linked to the Bauhaus movement.

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_69f0d6226fe881908819197c9ef9ee04 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f66f23ea408190842e6631a8f5ac20 completed May 2, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2661874d8c8190b03d0b0d787e3adc completed June 8, 2026, 6:30 a.m.
NEDg Description generation batch_6a2665d3199481908fe32ef9959be303 completed June 8, 2026, 6:48 a.m.
NED2 Entity disambiguation (via description) batch_6a266a6166a08190a3ec83291c005e7b completed June 8, 2026, 7:08 a.m.
Created at: April 28, 2026, 6:52 p.m.