Triple
T37695228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady of Kettlethorpe |
E938909
|
entity |
| Predicate | notableBearerLaterTitle |
P22452
|
FINISHED |
| Object | Duchess of Lancaster |
E786639
|
NE 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: Duchess of Lancaster | Statement: [Lady of Kettlethorpe, notableBearerLaterTitle, Duchess of Lancaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerLaterTitle Context triple: [Lady of Kettlethorpe, notableBearerLaterTitle, Duchess of Lancaster]
-
A.
notableBearerFullName
Indicates that a full personal name is that of a notable or well-known bearer associated with the referenced entity.
-
B.
notableBearerOfRole
Indicates that an entity is a particularly prominent or well-known holder or performer of a specified role.
-
C.
hasNotableBearerTitle
Indicates that an entity is associated with a notable person or group who holds a specific title or designation.
-
D.
notableTitleHeld
Indicates that an entity has held a distinguished or noteworthy title, rank, or official position.
-
E.
laterTitleHolder
chosen
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
- F. None of above.
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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cdc2c4188190be09e6a510c0c567 |
completed | June 28, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.