Triple
T36736255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Wedding of Prince William and Catherine Middleton |
E907485
|
entity |
| Predicate | brideMother |
P149460
|
FINISHED |
| Object | Carole Middleton |
—
|
NE NERFINISHED |
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: Carole Middleton | Statement: [Royal Wedding of Prince William and Catherine Middleton, brideMother, Carole Middleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brideMother Context triple: [Royal Wedding of Prince William and Catherine Middleton, brideMother, Carole Middleton]
-
A.
bride
Indicates that an entity is a woman who is getting married or has just been married in relation to a wedding event or spouse.
-
B.
brideFamily
chosen
Indicates a familial relationship in which one party is the family or relatives of the bride in a marriage context.
-
C.
heirMotherOf
Indicates that one entity is the mother of another entity who is designated as an heir.
-
D.
isMaternalFigureOf
Indicates a nurturing, protective, and guiding parental-like relationship that one individual has toward another, typically in a motherly role.
-
E.
spouseMother
Indicates that one person is the mother of another person’s spouse.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.