Triple
T28842778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Chandos |
E728364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hereditary title in the Peerage of Great Britain |
C672
|
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 title in the Peerage of Great Britain Context triple: [Duke of Chandos, instanceOf, hereditary title in the Peerage of Great Britain]
-
A.
peerage title
chosen
A peerage title is a hereditary or life rank of nobility granted by a sovereign, conferring social status and often certain legal or ceremonial privileges within a hierarchical aristocratic system.
-
B.
system of hereditary titles
A system of hereditary titles is a structured hierarchy of ranks and honors that are legally or socially passed down through family lines, typically from one generation to the next.
-
C.
earldom in the Peerage of England
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.
-
D.
Scottish hereditary office
A Scottish hereditary office is a formal position within Scotland’s historical or legal framework that is passed down through generations of a family, often carrying ceremonial, administrative, or feudal responsibilities.
-
E.
record for hereditary aristocratic titles
A record for hereditary aristocratic titles stores structured information about noble ranks, their holders, succession lines, and associated privileges across generations.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:41 a.m.