Triple
T37536286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustus FitzClarence |
E933205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | illegitimate child of British royalty |
C24003
|
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: illegitimate child of British royalty Context triple: [Augustus FitzClarence, instanceOf, illegitimate child of British royalty]
-
A.
illegitimate royal descendant
chosen
An illegitimate royal descendant is a person born outside of lawful marriage to a member of a royal family, who may possess royal blood but typically lacks formal dynastic rights or recognition.
-
B.
British princess
A British princess is a female member of the British royal family, typically bearing the title by birth or marriage and undertaking ceremonial, charitable, and representational duties on behalf of the monarchy.
-
C.
member of the English royal family
A member of the English royal family is an individual related by blood or legally recognized ties to the reigning monarch, holding a formal or ceremonial position within the United Kingdom’s constitutional monarchy.
-
D.
German-born British royal
A German-born British royal is a member of the British royal family who was born in a German state or territory and typically has familial, cultural, or dynastic ties to both Germany and the United Kingdom.
-
E.
legitimized royal child
A legitimized royal child is an offspring of a monarch or royal family member who was originally born outside of lawful marriage but has been formally granted legal and dynastic recognition, often including certain titles, rights, or succession privileges.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.