Triple
T33547532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catherine Anne Phipps |
E859244
|
entity |
| Predicate | honorificPrefixByMarriage |
P150114
|
FINISHED |
| Object | Lady Prevost |
—
|
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: Lady Prevost | Statement: [Catherine Anne Phipps, honorificPrefixByMarriage, Lady Prevost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificPrefixByMarriage Context triple: [Catherine Anne Phipps, honorificPrefixByMarriage, Lady Prevost]
-
A.
honorificPrefixOfSpouse
chosen
Indicates that a specified honorific prefix (e.g., Mr., Dr., Lady) is used as the formal title for a person’s spouse.
-
B.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
C.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
D.
honorificPartOfName
Indicates that an honorific title or form of address is included as part of a person's full name.
-
E.
honorificPrefixOfFather
Indicates that the subject is an honorific prefix or title used before the name of the object’s father.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:39 a.m.