Triple
T35249459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łęczyca castellany |
E1018055
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval administrative district |
C65150
|
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: medieval administrative district Context triple: [Łęczyca castellany, instanceOf, medieval administrative district]
-
A.
medieval Norwegian administrative district
A medieval Norwegian administrative district was a territorial unit used by the crown and local authorities to organize governance, taxation, justice, and military obligations within a defined region.
-
B.
medieval urban district
A medieval urban district is a distinct, often walled or gated, neighborhood within a medieval town or city characterized by its specific social, economic, or administrative functions and spatial organization.
-
C.
medieval county
A medieval county is a territorial and administrative unit governed by a count or similar noble, encompassing lands, settlements, and jurisdictions within a feudal hierarchy.
-
D.
medieval duchy
A medieval duchy is a territorial domain ruled by a duke or duchess, typically semi-autonomous within a larger kingdom or empire, with its own feudal hierarchy, laws, and military obligations.
-
E.
administrative district of the Holy Roman Empire
An administrative district of the Holy Roman Empire was a territorial unit governed by imperial or local authorities to organize political, judicial, and fiscal control within the Empire’s decentralized structure.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.