Triple
T37021312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trier Government Region |
E916227
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative region of Germany |
C9392
|
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: former administrative region of Germany Context triple: [Trier Government Region, instanceOf, former administrative region of Germany]
-
A.
administrative region of Germany
chosen
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.
-
B.
former German territory
A former German territory is a geographic area that was once under German sovereignty or administration but no longer belongs to Germany due to historical border changes, treaties, or decolonization.
-
C.
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.
-
D.
state of Germany
A state of Germany is a federal constituent entity (Bundesland) with its own government, constitution, and administrative responsibilities within the Federal Republic of Germany.
-
E.
constituent state of the German Empire
A constituent state of the German Empire was one of the semi-autonomous kingdoms, grand duchies, duchies, principalities, free Hanseatic cities, or imperial territories that together formed the federal structure of the German Empire from 1871 to 1918.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.