Triple
T13463818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Rutland |
E311439
|
entity |
| Predicate | hasFamilySeatSinceCentury |
P110466
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Dukes of Rutland, hasFamilySeatSinceCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilySeatSinceCentury Context triple: [Dukes of Rutland, hasFamilySeatSinceCentury, 16th century]
-
A.
hasSeatSinceYear
Indicates that an entity has continuously held a seat or position starting from a specified year.
-
B.
formerFamilySeat
Indicates that a location was previously the principal residence or ancestral home of a particular family but no longer holds that status.
-
C.
hasHistoricalSeat
Indicates that an entity possesses or is associated with a historically significant seat, location, or place of authority.
-
D.
familySeatFunction
Indicates that a location serves as the principal seat, residence, or base associated with a particular family or lineage.
-
E.
familySeat
Indicates the traditional principal residence or ancestral home associated with a particular family or lineage.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0f1830819085700b4521e44678 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:41 p.m.