Triple
T13885396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bezirk Rheinhessen-Pfalz |
E333827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former subdivision of a country |
C34305
|
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 subdivision of a country Context triple: [Bezirk Rheinhessen-Pfalz, instanceOf, former subdivision of a country]
-
A.
former subdivision
A former subdivision is an administrative or territorial unit that once existed as a distinct part of a larger entity but has since been dissolved, merged, or reorganized and no longer functions in its original capacity.
-
B.
subdivision of a duchy
A subdivision of a duchy is an administrative or territorial unit within a duchy, governed by local authorities under the overarching jurisdiction of the duke.
-
C.
former subdivision of the Russian Empire
A former subdivision of the Russian Empire is an obsolete administrative-territorial unit that once functioned as part of the empire’s governmental structure but no longer exists in its original form.
-
D.
former subdivision of the Kingdom of Poland
A former subdivision of the Kingdom of Poland is an historical administrative unit that once functioned as part of the kingdom’s territorial organization but no longer exists in its original form.
-
E.
overseas territory subdivision
An overseas territory subdivision is an administrative division of a country located outside its mainland, typically subject to the sovereign state's authority while often possessing distinct legal, political, or cultural arrangements.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.