Triple
T19536741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Davina Windsor |
E488785
|
entity |
| Predicate | spouseSeparation |
P493
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Lady Davina Windsor, spouseSeparation, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseSeparation Context triple: [Lady Davina Windsor, spouseSeparation, 2018]
-
A.
divorce
Indicates the legal dissolution of a marriage relationship between two spouses, ending their marital bond.
-
B.
maritalIssue
Indicates a relationship where there is conflict, dissatisfaction, or significant strain within a marital or committed partnership.
-
C.
spouseRelationshipEnd
chosen
Indicates that a marital relationship between two individuals has ended, such as through divorce, annulment, or separation.
-
D.
familyDivision
Indicates a relationship where a family is split into distinct parts or groups, often due to conflict, separation, or differing affiliations.
-
E.
divorceReason
Indicates the reason or cause for which a marriage ended in divorce between two individuals.
- F. None of above.
Provenance (3 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6386f0fac819081bbc29172c8965e |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.