Triple
T32584146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Viscount Keppel |
E832872
|
entity |
| Predicate | ennobledIn |
P154954
|
FINISHED |
| Object | 1782 |
—
|
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: 1782 | Statement: [1st Viscount Keppel, ennobledIn, 1782]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ennobledIn Context triple: [1st Viscount Keppel, ennobledIn, 1782]
-
A.
nobleTitleGranted
chosen
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or authority.
-
B.
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.
-
C.
nobleTitleAcquiredThrough
Indicates the manner, event, or process by which a person comes to obtain or be granted a particular noble title.
-
D.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
-
E.
elevatedToDukedom
Indicates that an entity has been raised or promoted to the rank or title of a dukedom.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66c41b481908abc65d5d284bcee |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.