Triple
T26842809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reckenwalde |
E675829
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical German name |
C22842
|
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: historical German name Context triple: [Reckenwalde, instanceOf, historical German name]
-
A.
former German name of a town
chosen
A former German name of a town is a historical place-name once used in the German language for a specific settlement, typically replaced after political, territorial, or cultural changes.
-
B.
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.
-
C.
German-language given name and surname combination
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.
-
D.
German noble
A German noble is a member of the historical aristocratic class in German-speaking regions, traditionally holding hereditary titles, land, and social privileges within the feudal and later monarchical systems.
-
E.
historical ethnonym
A historical ethnonym is a name or label historically used to designate a particular ethnic group, people, or population, often reflecting past cultural, political, or linguistic contexts that may differ from present-day usage.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:09 a.m.