Triple

T29079758
Position Surface form Disambiguated ID Type / Status
Subject Heinrich Schmidt E733938 entity
Predicate hasVariantSpelling P457 FINISHED
Object Heinrich Schmit
Heinrich Schmit is an individual whose name is a variant spelling of Heinrich Schmidt, a common German personal name.
E2293549 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: Heinrich Schmit | Statement: [Heinrich Schmidt, hasVariantSpelling, Heinrich Schmit]
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: Heinrich Schmit
Triple: [Heinrich Schmidt, hasVariantSpelling, Heinrich Schmit]
Generated description
Heinrich Schmit is an individual whose name is a variant spelling of Heinrich Schmidt, a common German personal 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_69f05b0c0f28819086eae6e84f2ae472 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f66142a7dc8190a574168fff93191f completed May 2, 2026, 8:40 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7abf397ddc8190bccbc1b969dc7d6f completed Aug. 11, 2026, 6:20 a.m.
NEDg Description generation batch_6a7abf9572ec8190b532134d5bac54d8 completed Aug. 11, 2026, 6:22 a.m.
NED2 Entity disambiguation (via description) batch_6a7abfd9f56c81908f24f347dad9882d completed Aug. 11, 2026, 6:23 a.m.
Created at: April 28, 2026, 10:53 a.m.