Triple
T26179637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Sheffield |
E654636
|
entity |
| Predicate | paternalFamilyTitle |
P20415
|
FINISHED |
| Object | Duke of Buckingham and Normanby |
—
|
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: Duke of Buckingham and Normanby | Statement: [Mary Sheffield, paternalFamilyTitle, Duke of Buckingham and Normanby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paternalFamilyTitle Context triple: [Mary Sheffield, paternalFamilyTitle, Duke of Buckingham and Normanby]
-
A.
paternalTitleFamily
Indicates a familial relationship where one entity holds a paternal title (such as father, grandfather, or paternal ancestor) in relation to another within a family structure.
-
B.
fatherTitle
chosen
Indicates the formal title or designation held by a person's father.
-
C.
paternalTitleConnection
Indicates a relationship where one entity holds a paternal (father-related) title in connection to another entity.
-
D.
fatherTitleAtBirth
Indicates the formal title or honorific held by a person's father at the time of that person's birth.
-
E.
patriarchTitle
Indicates that one entity holds the role or title of patriarch in relation to another entity.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6e0768819088a0a5dd82390c09 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:39 p.m.