Triple
T35242696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund de la Pole, 3rd Duke of Suffolk |
E1017569
|
entity |
| Predicate | reducedTitle |
P78065
|
FINISHED |
| Object | Earl 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: Earl of Suffolk | Statement: [Edmund de la Pole, 3rd Duke of Suffolk, reducedTitle, Earl of Suffolk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducedTitle Context triple: [Edmund de la Pole, 3rd Duke of Suffolk, reducedTitle, Earl of Suffolk]
-
A.
reducedVersionOf
Indicates that one entity is a simplified, shortened, or otherwise less extensive form of another entity while preserving its essential content or function.
-
B.
secondShortTitle
chosen
Indicates that an entity has a secondary or alternative short title associated with it.
-
C.
commonTitle
Indicates that two or more entities share the same title or designation.
-
D.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
E.
singleTitle
Indicates that an entity holds exactly one official title or designation within a given context.
- 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.