Triple
T7843563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Alfred, Duke of Edinburgh |
E181863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Saxe-Coburg and Gotha |
C23010
|
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 Saxe-Coburg and Gotha Context triple: [Prince Alfred, Duke of Edinburgh, instanceOf, Duke of Saxe-Coburg and Gotha]
-
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 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.
-
C.
Duke of Gloucester
The Duke of Gloucester is a noble title in the British peerage traditionally granted to junior members of the royal family, historically associated with high status, military service, and close proximity to the monarch.
-
D.
Duke of Connaught and Strathearn
The Duke of Connaught and Strathearn is a British royal dukedom historically granted to a male member of the royal family, associated with the regions of Connaught in Ireland and Strathearn in Scotland.
-
E.
King of Hanover
The King of Hanover was the hereditary monarch and head of state of the Kingdom of Hanover, a German kingdom that existed from 1814 to 1866, ruling over its government, military, and foreign affairs.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:48 p.m.