Triple
T1624698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Leipzig |
E35114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rural district of Germany |
C11185
|
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: rural district of Germany Context triple: [District of Leipzig, instanceOf, rural district of Germany]
-
A.
region of Germany
A region of Germany is a geographically and culturally distinct area within the country, often defined by historical boundaries, administrative divisions, or shared economic and social characteristics.
-
B.
region of Bavaria
A region of Bavaria is a geographically and administratively defined area within the German federal state of Bavaria, characterized by shared cultural, historical, and economic features.
-
C.
administrative region of Germany
An administrative region of Germany is a territorial unit within a federal state (Land) that serves as an intermediate level of government for coordinating regional administration, planning, and public services.
-
D.
natural region of Germany
A natural region of Germany is a geographically distinct area defined by its characteristic landscape, geology, climate, and ecosystems, rather than by political or administrative boundaries.
-
E.
administrative region of Bavaria
An administrative region of Bavaria is a territorial subdivision within the German state of Bavaria that serves as an intermediate level of government, coordinating regional administration, planning, and public services across its constituent districts and municipalities.
- F. None of above. chosen
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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.