Triple
T26156172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priscilla Anne Wellesley-Pole |
E659966
|
entity |
| Predicate | nobleStyleAfterMarriage |
P76052
|
FINISHED |
| Object | Countess of Westmorland |
—
|
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: Countess of Westmorland | Statement: [Priscilla Anne Wellesley-Pole, nobleStyleAfterMarriage, Countess of Westmorland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleStyleAfterMarriage Context triple: [Priscilla Anne Wellesley-Pole, nobleStyleAfterMarriage, Countess of Westmorland]
-
A.
aristocraticTitleBeforeMarriage
Indicates that the subject held a specific aristocratic title prior to entering into marriage.
-
B.
spouseNameAfterEnnoblement
Indicates that the predicate specifies the spouse’s name as it is used after the spouse has been ennobled or granted a noble title.
-
C.
spouseNobilityStatus
Indicates that the predicate specifies the nobility rank or noble status held by a person’s spouse.
-
D.
maritalStyleOf
Indicates the characteristic manner, pattern, or quality of interaction that defines a particular marriage or marital relationship.
-
E.
nobleTitleStyle
chosen
Indicates the specific form or style in which a person's noble title is expressed or formally rendered.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c0fd6a08190bafd573b07bb2fe8 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:27 p.m.