Triple
T33484024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Jenkins of Hillhead |
E857560
|
entity |
| Predicate | lifePeerageCreatedFor |
P37952
|
FINISHED |
| Object | Roy Jenkins |
—
|
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: Roy Jenkins | Statement: [Baron Jenkins of Hillhead, lifePeerageCreatedFor, Roy Jenkins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifePeerageCreatedFor Context triple: [Baron Jenkins of Hillhead, lifePeerageCreatedFor, Roy Jenkins]
-
A.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
B.
peerageForLife
chosen
Indicates that an individual holds a noble title or rank granted for the duration of their lifetime only, without hereditary succession.
-
C.
dateOfElevationToPeerage
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
D.
linkedToPeerage
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
-
E.
aristocraticTitleCreatedFrom
Indicates that an aristocratic title originates from, or was formally established based on, another specified source title or 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e531be388190b1b4a0cb1bc1da75 |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.