Triple
T11841567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean kingdoms |
E281664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval states |
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: medieval states Context triple: [Korean kingdoms, instanceOf, medieval states]
-
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.
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.
-
C.
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.
-
D.
medieval region
A medieval region is a geographically defined area during the Middle Ages characterized by distinct political authority, social structures, economic systems, and cultural practices within the broader feudal landscape.
-
E.
medieval political status
Medieval political status refers to the hierarchical position and associated rights, duties, and privileges of individuals or groups within the feudal and monarchical power structures 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.