Triple
T31676238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Richter |
E808406
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German-language surname and given-name combination |
C33835
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: German-language surname and given-name combination Context triple: [Thomas Richter, instanceOf, German-language surname and given-name combination]
-
A.
German-language given name and surname combination
chosen
A German-language given name and surname combination is a full personal name constructed from a first name and a family name that both originate from or are commonly used in German-speaking regions.
-
B.
Hungarian-language surname–given name combination
A Hungarian-language surname–given name combination is a personal name structure in which the family name precedes the given name, following Hungarian naming conventions and orthographic rules.
-
C.
surname of German origin
A surname of German origin is a family name derived from the German language and cultural or geographic roots within German-speaking regions.
-
D.
Old High German personal name
An Old High German personal name is a given name used by German-speaking peoples between roughly the 6th and 11th centuries, typically formed from meaningful Germanic word elements reflecting traits, virtues, or social roles.
-
E.
Scandinavian given name and surname
A Scandinavian given name and surname is a personal name of Nordic origin commonly used both as a first name and a family name in countries such as Sweden, Norway, and Denmark.
- F. None of above.
Provenance (1 batch)
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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:03 p.m.