Triple
T34903273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiona Mary Campbell, 22nd Countess of Loudoun |
E1006650
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hereditary noblewoman |
C2524
|
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: hereditary noblewoman Context triple: [Fiona Mary Campbell, 22nd Countess of Loudoun, instanceOf, hereditary noblewoman]
-
A.
hereditary princess
A hereditary princess is a royal woman who holds her title by birthright within a monarchy’s line of succession, typically as the daughter or designated female heir of a reigning or titled sovereign.
-
B.
noblewoman
chosen
A noblewoman is a woman of high social rank or aristocratic birth who holds hereditary or granted titles, privileges, and responsibilities within a hierarchical society.
-
C.
daughter of a count
A daughter of a count is a noblewoman born into the rank of countship, typically holding the courtesy title of lady and enjoying the social status and privileges associated with the aristocracy.
-
D.
Georgian noblewoman
A Georgian noblewoman is an aristocratic woman from the historical region of Georgia, typically characterized by high social status, landownership, and influence within the political and cultural life of Georgian society.
-
E.
9th-century noblewoman
A 9th-century noblewoman is an aristocratic woman of high social rank who manages estates, forges political alliances through marriage and kinship, and upholds the cultural, religious, and economic interests of her noble household within a feudal or proto-feudal society.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.