Triple
T28027552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Elizabeth Egerton |
E708165
|
entity |
| Predicate | dynastyOrHouse |
P20125
|
FINISHED |
| Object | Egerton family |
—
|
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: Egerton family | Statement: [Lady Elizabeth Egerton, dynastyOrHouse, Egerton family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyOrHouse Context triple: [Lady Elizabeth Egerton, dynastyOrHouse, Egerton family]
-
A.
dynasticHouseInvolved
Indicates that a particular dynastic house (royal or noble lineage) is involved in, associated with, or plays a role in the referenced event, entity, or relationship.
-
B.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
-
C.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
D.
dynasticOrigin
chosen
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
E.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 8:13 p.m.