Triple
T12581070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Elizabeth Cavendish |
E300335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Georgian nobility |
C32176
|
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: member of the Georgian nobility Context triple: [Lady Elizabeth Cavendish, instanceOf, member of the Georgian nobility]
-
A.
member of German nobility
A member of German nobility is an individual belonging to a historically privileged social class in German-speaking regions, typically holding hereditary titles, land, and social status recognized under traditional aristocratic systems.
-
B.
member of the Burgundian nobility
A member of the Burgundian nobility is an individual belonging to the hereditary aristocratic elite of the historical Duchy or County of Burgundy, holding land, titles, and social privileges within its feudal hierarchy.
-
C.
medieval Georgian noblewoman
A medieval Georgian noblewoman is an aristocratic woman of the Georgian kingdoms who held social status, land-related privileges, and dynastic responsibilities within the feudal and courtly structures of the Middle Ages.
-
D.
Serbian nobleman
A Serbian nobleman is a member of the historical or contemporary Serbian aristocracy, typically holding hereditary titles, land, and social privileges within Serbian society.
-
E.
member of the Roman nobility
A member of the Roman nobility is an individual belonging to the elite social class of ancient Rome, distinguished by hereditary status, political influence, and privileged legal and economic rights.
- F. None of above. chosen
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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:02 p.m.