Triple
T28366364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Oliver Saville, Baron Saville of Newdigate |
E718499
|
entity |
| Predicate | appointedToPeerage |
P116702
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Mark Oliver Saville, Baron Saville of Newdigate, appointedToPeerage, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedToPeerage Context triple: [Mark Oliver Saville, Baron Saville of Newdigate, appointedToPeerage, 1997]
-
A.
elevatedToPeerageFor
Indicates that a person was granted a noble title or peerage specifically as a result of, or in recognition for, a particular reason, action, or service.
-
B.
appointedToPrivyCouncil
Indicates that an individual has been formally appointed as a member of the Privy Council.
-
C.
appointedKnightOfTheGarter
Indicates that an entity has been formally appointed as a Knight of the Order of the Garter.
-
D.
conveysPeerage
Indicates that one entity formally grants or transfers a noble title or rank of peerage to another entity.
-
E.
hasPeerageTitle
chosen
Indicates that an entity holds or is associated with a formal noble or aristocratic title within a peerage system.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 12:55 a.m.