Triple
T33235856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Household of the Queen consort |
E850824
|
entity |
| Predicate | notableQueenConsortsServed |
P206397
|
FINISHED |
| Object | Catherine of Aragon |
E74286
|
NE 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: Catherine of Aragon | Statement: [Household of the Queen consort, notableQueenConsortsServed, Catherine of Aragon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableQueenConsortsServed Context triple: [Household of the Queen consort, notableQueenConsortsServed, Catherine of Aragon]
-
A.
producedQueenConsort
Indicates that one entity gave rise to or is the origin of another entity who became a queen consort.
-
B.
spouseIsQueenConsortOf
Indicates that a person’s spouse holds the title and role of queen consort in relation to a specific monarch.
-
C.
spouseServedMonarch
Indicates that the spouse of a person held a position of service or duty to a monarch.
-
D.
monarchOfWhomConsort
Indicates that a person is the monarch (king/queen/ruler) of another person who is their consort (spouse).
-
E.
marriedToMonarchFrom
Indicates that a person is married to a monarch who rules or comes from a specified country or region.
- F. None of above. chosen
Provenance (5 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352fde7c188190b5bf2a75011abad7 |
completed | June 19, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:31 a.m.