Triple

T32392589
Position Surface form Disambiguated ID Type / Status
Subject Krause E827713 entity
Predicate hasNotableBearer P458 FINISHED
Object Hans-Henning von der Osten-Krause
Hans-Henning von der Osten-Krause is a notable individual associated with the German surname Krause, recognized as a distinguished bearer of that family name.
E2292927 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: Hans-Henning von der Osten-Krause | Statement: [Krause, hasNotableBearer, Hans-Henning von der Osten-Krause]
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: Hans-Henning von der Osten-Krause
Triple: [Krause, hasNotableBearer, Hans-Henning von der Osten-Krause]
Generated description
Hans-Henning von der Osten-Krause is a notable individual associated with the German surname Krause, recognized as a distinguished bearer of that family name.

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_69f349184e7481909c6c54428cb9cf12 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c20f209081909fb9ac8f95069f04 completed May 3, 2026, 3:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a7a438943e08190bf0ae7a602ec3ff5 completed Aug. 10, 2026, 9:32 p.m.
NEDg Description generation batch_6a7a445bc9e881909f6d446aee6b5edf completed Aug. 10, 2026, 9:36 p.m.
NED2 Entity disambiguation (via description) batch_6a7a45071a8481908bd8cb55371c3d2c completed Aug. 10, 2026, 9:39 p.m.
Created at: May 1, 2026, 12:52 a.m.