Triple
T36005850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earldom of Leicester |
E1041269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | English earldom |
C51767
|
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: English earldom Context triple: [Earldom of Leicester, instanceOf, English earldom]
-
A.
Scottish earldom
A Scottish earldom is a hereditary noble title in the peerage of Scotland, historically granting its holder territorial authority, social precedence, and certain feudal or ceremonial privileges within the Scottish realm.
-
B.
earldom in the Peerage of England
chosen
An earldom in the Peerage of England is a hereditary noble title of earl rank, created by the English Crown and forming part of the traditional hierarchy of English nobility below marquess and above viscount.
-
C.
medieval English noble dynasty
A medieval English noble dynasty is a powerful hereditary family line that held titles, lands, and political influence across generations in England during the Middle Ages.
-
D.
9th-century English noble
A 9th-century English noble is a high-ranking landowning aristocrat in early medieval England who wields military, judicial, and political authority under a king within a fragmented and often war-torn landscape.
-
E.
Anglo-Breton noble
An Anglo-Breton noble is a medieval aristocrat of mixed English and Breton heritage who held land, titles, and political influence across both regions, often serving as a cultural and military intermediary between them.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.