Triple
T27240844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | le Boteler |
E687203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval surname |
C51434
|
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 surname Context triple: [le Boteler, instanceOf, medieval surname]
-
A.
medieval English name
A medieval English name is a personal name used in England roughly between the 5th and 15th centuries, often reflecting Old English, Norman, or Latin influences and frequently tied to religious, occupational, or locational origins.
-
B.
medieval Latin name
A medieval Latin name is a personal or place designation used in the Middle Ages, typically rendered in Latinized form to align with ecclesiastical, scholarly, or administrative conventions of the period.
-
C.
Anglo-Norman surname
chosen
An Anglo-Norman surname is a family name of Norman French origin that became established in England and surrounding regions following the Norman Conquest, often reflecting Norman personal names, occupations, or places.
-
D.
surname of Anglo-Saxon origin
A surname of Anglo-Saxon origin is a family name derived from the Old English language and early medieval English culture, often based on occupations, locations, personal characteristics, or patronymic forms.
-
E.
medieval ruling family
A medieval ruling family is a hereditary dynasty that holds political power, land, and social authority over a realm, often legitimized by lineage, religion, and military strength.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 10:37 a.m.