Triple
T2827042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Alexandra, The Honourable Lady Ogilvy |
E54946
|
entity |
| Predicate | parentOfRoyalDescendants |
P42702
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [Princess Alexandra, The Honourable Lady Ogilvy, parentOfRoyalDescendants, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentOfRoyalDescendants Context triple: [Princess Alexandra, The Honourable Lady Ogilvy, parentOfRoyalDescendants, yes]
-
A.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
B.
childOfMonarch
Indicates that one entity is the offspring (biological or legally recognized) of another entity who holds or held the status of monarch.
-
C.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
D.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
E.
monarchIsParentOf
Indicates that a monarch has a parent-child relationship with another individual, where the monarch is the parent.
- F. None of above. chosen
Provenance (4 batches)
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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde94ba848190b2c990936e07e6bb |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddccd50c8190a975942f46cfc01f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 9:59 p.m.