Triple
T6678674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Arthur, Duke of Connaught and Strathearn |
E151922
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Connaught and Strathearn |
C21183
|
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: Duke of Connaught and Strathearn Context triple: [Prince Arthur, Duke of Connaught and Strathearn, instanceOf, Duke of Connaught and Strathearn]
-
A.
Duke of Kent
The Duke of Kent is a hereditary noble title in the British peerage traditionally granted to a close male relative of the reigning monarch, historically associated with high social rank, landholdings, and ceremonial duties.
-
B.
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.
-
C.
Duke of Fife
The Duke of Fife is a hereditary title in the Peerage of the United Kingdom, traditionally associated with the Fife region of Scotland and historically granted to members of the British royal family or their close relatives.
-
D.
Duke of Edinburgh
The Duke of Edinburgh is a noble title in the British peerage traditionally granted to a senior member of the royal family, historically associated with significant public service and ceremonial duties.
-
E.
Duke of York
The Duke of York is a noble title in the British peerage traditionally granted to the second son of the reigning monarch, historically associated with significant political and military influence.
- 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_69c687f830bc81909eb8b04dbb8450b1 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:03 p.m.