Triple
T35242695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund de la Pole, 3rd Duke of Suffolk |
E1017569
|
entity |
| Predicate | lostTitleToCrown |
P73248
|
FINISHED |
| Object | Dukedom of Suffolk |
—
|
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: Dukedom of Suffolk | Statement: [Edmund de la Pole, 3rd Duke of Suffolk, lostTitleToCrown, Dukedom of Suffolk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostTitleToCrown Context triple: [Edmund de la Pole, 3rd Duke of Suffolk, lostTitleToCrown, Dukedom of Suffolk]
-
A.
lostThroneTo
Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
-
B.
titleForfeited
chosen
Indicates that an entity has lost or been stripped of a title or formal designation it previously held.
-
C.
loserTitle
Indicates the title, label, or designation assigned to the losing party in a competition, contest, or comparison.
-
D.
claimedTitle
Indicates that an entity asserts or declares possession of a particular title or rank.
-
E.
titleReign
Indicates the period during which a particular title was officially held or exercised by an entity.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.