Triple
T35259247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czersk castellany |
E1018325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval military 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 military district Context triple: [Czersk castellany, instanceOf, medieval military district]
-
A.
medieval administrative district
chosen
A medieval administrative district is a defined territorial unit governed by local officials on behalf of a monarch or lord, used to organize taxation, justice, and military obligations.
-
B.
military district of the Holy Roman Empire
A military district of the Holy Roman Empire was an administrative and territorial unit organized primarily for defense and military command, grouping various imperial estates under a regional military structure.
-
C.
medieval military force
A medieval military force is an organized body of armed personnel, including knights, infantry, archers, and support units, raised and commanded by a lord, king, or other authority to wage war, defend territory, and enforce political power during the Middle Ages.
-
D.
Carolingian frontier march
A Carolingian frontier march was a militarized border territory of the Carolingian Empire, governed by a margrave and designed to defend and expand imperial frontiers.
-
E.
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.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.