Triple
T30610246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Waldegrave Palmer, 2nd Viscount Wolmer |
E779158
|
entity |
| Predicate | titleAfterSuccession |
P8415
|
FINISHED |
| Object | 2nd Earl of Selborne |
—
|
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: 2nd Earl of Selborne | Statement: [William Waldegrave Palmer, 2nd Viscount Wolmer, titleAfterSuccession, 2nd Earl of Selborne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleAfterSuccession Context triple: [William Waldegrave Palmer, 2nd Viscount Wolmer, titleAfterSuccession, 2nd Earl of Selborne]
-
A.
successorTitle
chosen
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
B.
titleHeldBeforeSuccession
Indicates that an entity held a specific title or position prior to a particular succession event.
-
C.
successorTitleContext
Indicates the contextual circumstances or framework under which one title succeeds another.
-
D.
titleAfterExile
Indicates that an entity holds or receives a particular title only after a period of exile has occurred.
-
E.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 29, 2026, 8:26 p.m.