Triple
T32911876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baroness Amos |
E841898
|
entity |
| Predicate | createdPeerageType |
P3782
|
FINISHED |
| Object | life peerage |
—
|
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: life peerage | Statement: [Baroness Amos, createdPeerageType, life peerage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdPeerageType Context triple: [Baroness Amos, createdPeerageType, life peerage]
-
A.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
B.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
C.
peerageCreationContext
Indicates the circumstances or setting in which a peerage title is established or conferred.
-
D.
createdBaronet
Indicates that one entity formally established or granted a baronetcy title to another entity.
-
E.
typeOfPeerage
chosen
Indicates the specific rank or category within a system of peerage that a given title or noble status belongs to.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 1, 2026, 1:19 a.m.