Triple
T16059779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Hertford |
E389577
|
entity |
| Predicate | linkedFamilySeat |
P1912
|
FINISHED |
| Object | Seymour family estates |
—
|
LITERAL FINISHED |
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: Seymour family estates | Statement: [Earl of Hertford, linkedFamilySeat, Seymour family estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedFamilySeat Context triple: [Earl of Hertford, linkedFamilySeat, Seymour family estates]
-
A.
familySeat
chosen
Indicates the traditional principal residence or ancestral home associated with a particular family or lineage.
-
B.
familySeatFunction
Indicates that a location serves as the principal seat, residence, or base associated with a particular family or lineage.
-
C.
familySeatGiftedBy
Indicates that a family seat (such as an estate or ancestral property) was granted or given to someone by a specified donor.
-
D.
linkedFamilyTitle
Indicates that one entity is associated with another through a family-related title or role (such as parent, sibling, or spouse).
-
E.
familySeatGiftedFor
Indicates that a family’s hereditary seat or estate was granted or bestowed to a recipient, rather than acquired by inheritance or purchase.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.