Triple

T31376629
Position Surface form Disambiguated ID Type / Status
Subject Schumann E800323 entity
Predicate hasNotableBearer P458 FINISHED
Object Friedrich Schumann
Friedrich Schumann is a notable individual who shares the Schumann surname, likely recognized for contributions in a specific professional or cultural field.
E1978821 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: Friedrich Schumann | Statement: [Schumann, hasNotableBearer, Friedrich Schumann]
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: Friedrich Schumann
Triple: [Schumann, hasNotableBearer, Friedrich Schumann]
Generated description
Friedrich Schumann is a notable individual who shares the Schumann surname, likely recognized for contributions in a specific professional or cultural field.

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_69f224e84da08190abfc2f17494a33c8 completed April 29, 2026, 3:34 p.m.
NER Named-entity recognition batch_69f69fecd8f081908a9452de3bb8ab7d completed May 3, 2026, 1:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2d9d317db08190b0787d8f416963af completed June 13, 2026, 6:10 p.m.
NEDg Description generation batch_6a2da12dbef48190831aab3e103444e7 completed June 13, 2026, 6:27 p.m.
NED2 Entity disambiguation (via description) batch_6a2dfbfc341881908d64ee9919122d25 completed June 14, 2026, 12:55 a.m.
Created at: April 29, 2026, 9:18 p.m.