Triple
T31907826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Yarborough |
E814600
|
entity |
| Predicate | createdForFamilyBranch |
P137265
|
FINISHED |
| Object | Pelham of Brocklesby |
—
|
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: Pelham of Brocklesby | Statement: [Baron Yarborough, createdForFamilyBranch, Pelham of Brocklesby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdForFamilyBranch Context triple: [Baron Yarborough, createdForFamilyBranch, Pelham of Brocklesby]
-
A.
createdForFamilyOf
chosen
Indicates that something was created or produced specifically for the benefit, use, or needs of a particular family or family group.
-
B.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
C.
heldByFamilyBranch
Indicates that something is possessed, controlled, or maintained by a specific branch or sub-lineage of a family.
-
D.
establishedAsBranchBy
Indicates that one entity was created or designated as a branch or subsidiary by another entity.
-
E.
basedOnFamilyOf
Indicates that one entity is derived from, modeled after, or determined by the family, lineage, or familial characteristics of 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, midnight