Triple
T18077288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Clermont-en-Beauvaisis |
E432586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval French territory |
C26318
|
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 French territory Context triple: [County of Clermont-en-Beauvaisis, instanceOf, medieval French territory]
-
A.
French kingdom
A French kingdom is a sovereign monarchical state centered on French territory and culture, ruled by a king whose authority shapes its political, social, and legal structures.
-
B.
medieval region
chosen
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.
former province of France
A former province of France is a historical territorial and administrative region that existed before the French Revolution, often retaining distinct cultural and regional identities despite no longer having official administrative status.
-
D.
medieval French dynasty
A medieval French dynasty is a ruling family that held hereditary power over French territories during the Middle Ages, shaping the kingdom’s political, social, and cultural development through successive generations of monarchs.
-
E.
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.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:26 a.m.