Triple
T11660609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conan IV, Duke of Brittany |
E277108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 12th-century noble |
C13168
|
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: 12th-century noble Context triple: [Conan IV, Duke of Brittany, instanceOf, 12th-century noble]
-
A.
12th-century monarch
A 12th-century monarch is a sovereign ruler who governed a kingdom or empire during the 1100s, wielding political, military, and often religious authority within a feudal and dynastic framework.
-
B.
12th-century noblewoman
A 12th-century noblewoman is an aristocratic woman of medieval Europe who wields social, economic, and sometimes political influence through landholding, marriage alliances, and the management of her household and estates within a feudal hierarchy.
-
C.
12th-century person
chosen
A 12th-century person is an individual who lived during the years 1101–1200 CE, shaped by the social, political, religious, and cultural contexts of the High Middle Ages.
-
D.
14th-century English noble
A 14th-century English noble is a high-ranking member of the medieval English aristocracy who holds land from the king, exercises local political and military authority, and participates in courtly and feudal obligations within a rigidly hierarchical society.
-
E.
11th-century noblewoman
An 11th-century noblewoman is a high-born female member of medieval European aristocracy whose life centers on managing estates, forging political alliances through marriage, and upholding social and religious obligations within a feudal hierarchy.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.