Triple
T4286850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peniston Lamb, 1st Viscount Melbourne |
E97289
|
entity |
| Predicate | elevationToPeerageAsBaronMelbourne |
P2735
|
FINISHED |
| Object | 1770 |
—
|
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: 1770 | Statement: [Peniston Lamb, 1st Viscount Melbourne, elevationToPeerageAsBaronMelbourne, 1770]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationToPeerageAsBaronMelbourne Context triple: [Peniston Lamb, 1st Viscount Melbourne, elevationToPeerageAsBaronMelbourne, 1770]
-
A.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
B.
dateOfElevationToPeerage
chosen
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
C.
createdBaronet
Indicates that one entity formally established or granted a baronetcy title to another entity.
-
D.
dateOfBaronetcy
Indicates the date on which a person was granted or created a baronetcy title.
-
E.
succeededByInMarquessate
Indicates that one entity was the immediate successor of another in holding a particular marquessate title.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3505d23d88190a638f2cc2acee9ee |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.