Triple
T30403626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Anne Seymour |
E773416
|
entity |
| Predicate | aristocraticHouseByMarriage |
P169167
|
FINISHED |
| Object | House of Osborne |
—
|
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: House of Osborne | Statement: [Lady Anne Seymour, aristocraticHouseByMarriage, House of Osborne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aristocraticHouseByMarriage Context triple: [Lady Anne Seymour, aristocraticHouseByMarriage, House of Osborne]
-
A.
aristocraticTitleByMarriage
Indicates that an individual holds an aristocratic title acquired through marriage rather than by birth or independent grant.
-
B.
spouseOfMonarchsFamily
Indicates that one person is the spouse of a member of a monarch’s family.
-
C.
royalHouseByFather
Indicates that an individual's royal house affiliation is determined through their father's royal lineage.
-
D.
royalHouseOfHusband
Indicates that the specified royal house is the dynastic or familial house to which the husband in the relationship belongs.
-
E.
relatedRoyalHouse
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861c95e88190a5f3a4a6c952692a |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:03 p.m.