Triple
T29952029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Savile |
E760793
|
entity |
| Predicate | familySeatHistoric |
P106565
|
FINISHED |
| Object | Rufford Abbey, Nottinghamshire |
—
|
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: Rufford Abbey, Nottinghamshire | Statement: [Baron Savile, familySeatHistoric, Rufford Abbey, Nottinghamshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familySeatHistoric Context triple: [Baron Savile, familySeatHistoric, Rufford Abbey, Nottinghamshire]
-
A.
familySeatHistorically
Indicates that a particular location historically served as the principal residence or ancestral seat of a specific family or lineage.
-
B.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
C.
capitalHistoric
Indicates that a location has served as a capital city at some point in history, even if it is not the current capital.
-
D.
historicalFamily
Indicates a familial relationship that existed between entities in the past, regardless of whether it still holds in the present.
-
E.
formerFamilySeat
chosen
Indicates that a location was previously the principal residence or ancestral home of a particular family but no longer holds that status.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 29, 2026, 6:26 p.m.