Triple
T37948175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Ponsonby, 1st Baron de Mauley |
E946665
|
entity |
| Predicate | elevationToPeerageChamber |
P180739
|
FINISHED |
| Object | House of Lords |
—
|
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: House of Lords | Statement: [Charles Ponsonby, 1st Baron de Mauley, elevationToPeerageChamber, House of Lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationToPeerageChamber Context triple: [Charles Ponsonby, 1st Baron de Mauley, elevationToPeerageChamber, House of Lords]
-
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.
elevation to peerage
chosen
Indicates the formal act of granting someone a noble title or rank, thereby raising them into the peerage.
-
C.
elevationToEarldom
Indicates the action or event of raising someone to the rank and title of earl.
-
D.
dateOfElevationToPeerage
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
E.
conveysPeerage
Indicates that one entity formally grants or transfers a noble title or rank of peerage to another 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:20 p.m.