Triple
T30305610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Mary Osborne |
E770772
|
entity |
| Predicate | isFromFamilyHeadedBy |
P25225
|
FINISHED |
| Object | Dukes of Leeds |
—
|
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: Dukes of Leeds | Statement: [Lady Mary Osborne, isFromFamilyHeadedBy, Dukes of Leeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromFamilyHeadedBy Context triple: [Lady Mary Osborne, isFromFamilyHeadedBy, Dukes of Leeds]
-
A.
hasFamilyHead
chosen
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
B.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
identifiedAsFamilyIn
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
-
E.
isFromFamilyKnownFor
Indicates that an entity belongs to a family that is widely recognized or notable for a particular characteristic, achievement, or reputation.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6816751548190b70eda0dd55be32d |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:49 p.m.