Triple
T33539197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangan Demesne |
E859023
|
entity |
| Predicate | formerFamilySeatOf |
P106565
|
FINISHED |
| Object | Wellesley 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: Wellesley family | Statement: [Dangan Demesne, formerFamilySeatOf, Wellesley family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerFamilySeatOf Context triple: [Dangan Demesne, formerFamilySeatOf, Wellesley family]
-
A.
formerFamilySeat
chosen
Indicates that a location was previously the principal residence or ancestral home of a particular family but no longer holds that status.
-
B.
nobleFamilySeat
Indicates the location that serves as the principal seat or main residence of a noble family.
-
C.
laterFamilySeat
Indicates that one entity serves as a subsequent or later seat, residence, or base for a particular family or lineage, following an earlier one.
-
D.
dynasticSeat
Indicates that a particular location serves as the principal seat of power or ruling center for a specific dynasty or ruling family.
-
E.
formerRulerHouse
Indicates that a person once ruled on behalf of, or as a member of, a particular ruling house or dynasty but no longer holds that ruling position.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.