Triple
T14494445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Feodor Alexandrovich of Russia |
E359454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | grandson of a monarch |
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: grandson of a monarch Context triple: [Prince Feodor Alexandrovich of Russia, instanceOf, grandson of a monarch]
-
A.
Georgian prince
A Georgian prince is a male member of the royal or noble families of Georgia, historically holding hereditary titles, political influence, and social prestige within the Georgian monarchy and aristocracy.
-
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.
royal prince
A royal prince is a male member of a monarchy’s ruling family, typically in the line of succession to the throne and bearing ceremonial, diplomatic, and sometimes administrative duties.
-
D.
younger son of a duke
A younger son of a duke is a male child born after the heir in a ducal family, typically holding a courtesy title and social rank below the eldest son but above most other nobles.
-
E.
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.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:21 a.m.