Triple
T8336777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Francis of Teck |
E195807
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the House of Teck |
C11665
|
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: member of the House of Teck Context triple: [Prince Francis of Teck, instanceOf, member of the House of Teck]
-
A.
member of extended royal family
A member of the extended royal family is an individual related by blood, marriage, or adoption to the reigning monarch or core royal line, but who holds a more distant position in the line of succession and typically fewer official duties.
-
B.
member of a royal family
chosen
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
-
C.
member of the House of Stuart
A member of the House of Stuart is an individual belonging by birth or legitimate descent to the royal dynasty that ruled Scotland and later England, Great Britain, and Ireland between the late 14th and early 18th centuries.
-
D.
British royal
A British royal is a member of the United Kingdom’s monarchy, typically born or married into the royal family, who embodies and represents national tradition, continuity, and ceremonial leadership.
-
E.
Princess of Saxe-Coburg-Saalfeld
A Princess of Saxe-Coburg-Saalfeld is a female member of the German ducal House of Saxe-Coburg-Saalfeld, typically by birth or marriage, holding the princely title associated with this historical Ernestine duchy.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:57 p.m.