Triple
T28027529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Jane Egerton |
E708164
|
entity |
| Predicate | notableFamilyHead |
P202331
|
FINISHED |
| Object | Scroop Egerton, 1st Duke of Bridgewater |
—
|
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: Scroop Egerton, 1st Duke of Bridgewater | Statement: [Lady Jane Egerton, notableFamilyHead, Scroop Egerton, 1st Duke of Bridgewater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFamilyHead Context triple: [Lady Jane Egerton, notableFamilyHead, Scroop Egerton, 1st Duke of Bridgewater]
-
A.
notableLeaderFamily
Indicates that a person belongs to the family of a notable or prominent leader.
-
B.
notableFamilyNameOf
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
-
C.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
-
D.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
E.
familyNotableMember
Indicates that a particular individual is a distinguished or noteworthy member of a given family.
- F. None of above. chosen
Provenance (4 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
| PDg | Predicate description generation | batch_6a00733756848190b94524b42d6edf0a |
completed | May 10, 2026, 11:59 a.m. |
Created at: April 27, 2026, 8:13 p.m.