Triple
T32822140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baroness Hood |
E839461
|
entity |
| Predicate | linkedMaleTitle |
P159734
|
FINISHED |
| Object | Baron Hood |
—
|
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: Baron Hood | Statement: [Baroness Hood, linkedMaleTitle, Baron Hood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedMaleTitle Context triple: [Baroness Hood, linkedMaleTitle, Baron Hood]
-
A.
officeHolderTitleWhenMale
Indicates the specific title used for a person holding an office when that office holder is male.
-
B.
hasMaleLineTitle
Indicates that a title is inherited or held exclusively through an unbroken male lineage from one male ancestor to his male descendants.
-
C.
linkedFamilyTitle
Indicates that one entity is associated with another through a family-related title or role (such as parent, sibling, or spouse).
-
D.
paternalTitleConnection
Indicates a relationship where one entity holds a paternal (father-related) title in connection to another entity.
-
E.
oppositeTitleByGender
chosen
Indicates that one title is the gender-based counterpart of another title (e.g., king/queen, actor/actress).
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 1:15 a.m.