Triple
T14949441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish principalities |
E372751
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | feudal polity |
C4114
|
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: feudal polity Context triple: [Polish principalities, instanceOf, feudal polity]
-
A.
medieval polity
chosen
A medieval polity is a territorially based political entity of the Middle Ages—such as a kingdom, duchy, city-state, or principality—defined by overlapping authorities, personal allegiances, and often fragmented sovereignty rather than a centralized nation-state structure.
-
B.
system of nobility
A system of nobility is a hierarchical social structure in which hereditary or granted titles confer formal ranks, privileges, and obligations within a society.
-
C.
feudal territories
Feudal territories are landholdings governed by lords who exercise political, economic, and judicial authority over the land and its inhabitants in exchange for loyalty and service within a hierarchical system.
-
D.
territorial lordship
Territorial lordship is a system of authority in which a lord exercises political, legal, and economic control over a defined geographic area and its inhabitants, typically by hereditary or feudal right.
-
E.
group of medieval polities
A group of medieval polities is a collection of semi-autonomous kingdoms, principalities, city-states, or other territorial entities that interacted through shifting alliances, conflicts, and hierarchies within the broader sociopolitical landscape of the Middle Ages.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:39 a.m.