Triple
T10181240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas FitzWilliam, 8th Viscount FitzWilliam |
E236786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Viscount FitzWilliam |
C27548
|
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: Viscount FitzWilliam Context triple: [Thomas FitzWilliam, 8th Viscount FitzWilliam, instanceOf, Viscount FitzWilliam]
-
A.
Earl of Oxford and Asquith
Earl of Oxford and Asquith is a British hereditary peerage title in the United Kingdom, created in 1925 for former Prime Minister H. H. Asquith, combining the historic earldom of Oxford with his family name.
-
B.
Earl of Orrery
The Earl of Orrery is a noble title in the Peerage of Ireland historically associated with the Boyle family, notably linked to political influence and the development of the mechanical model of the solar system known as an orrery.
-
C.
Duke of Penthièvre
The Duke of Penthièvre is a French noble title historically associated with a high-ranking peer of France, often linked to the House of Bourbon and significant territorial and political influence in Brittany.
-
D.
Duke of Argyll
The Duke of Argyll is a hereditary Scottish noble title historically held by the chief of Clan Campbell, traditionally associated with significant political influence, military leadership, and extensive landholdings in Argyll, Scotland.
-
E.
Duke of Richmond
The Duke of Richmond is a hereditary noble title in the Peerage of England, historically granted to members of the royal family or high-ranking aristocrats associated with the region of Richmond.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 9:11 p.m.