Triple
T25186458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Montargis |
E630731
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval territorial domain |
C6478
|
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 territorial domain Context triple: [Lordship of Montargis, instanceOf, medieval territorial domain]
-
A.
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.
-
B.
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.
-
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.
territorial lordship
chosen
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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:44 p.m.