Triple
T28340611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophia Alekseyevna |
E717799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the royal family |
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 royal family Context triple: [Sophia Alekseyevna, instanceOf, member of the royal family]
-
A.
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.
-
B.
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.
-
C.
member of a former royal family
A member of a former royal family is an individual descended from or previously holding status within a monarchy that has since lost its ruling power or official political authority.
-
D.
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.
-
E.
member of Thai royal family
A member of the Thai royal family is an individual who belongs by birth or marriage to the monarchy of Thailand, holding a recognized royal title and status under Thai royal and constitutional traditions.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 12:39 a.m.