Triple
T4286851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peniston Lamb, 1st Viscount Melbourne |
E97289
|
entity |
| Predicate | elevationToPeerageAsViscountMelbourne |
P2735
|
FINISHED |
| Object | 1781 |
—
|
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: 1781 | Statement: [Peniston Lamb, 1st Viscount Melbourne, elevationToPeerageAsViscountMelbourne, 1781]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationToPeerageAsViscountMelbourne Context triple: [Peniston Lamb, 1st Viscount Melbourne, elevationToPeerageAsViscountMelbourne, 1781]
-
A.
dateOfElevationToPeerage
chosen
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
B.
conveysPeerage
Indicates that one entity formally grants or transfers a noble title or rank of peerage to another entity.
-
C.
elevatedToDuchy
Indicates that a territory, region, or domain has been formally raised in rank or status to become a duchy.
-
D.
elevatedToPrincipalityBy
Indicates that an entity was raised in status or rank to a principality by another entity or authority.
-
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.