Triple
T12438381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alec Douglas-Home |
E297205
|
entity |
| Predicate | createdLifePeer |
P76080
|
FINISHED |
| Object | 1974 |
—
|
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: 1974 | Statement: [Alec Douglas-Home, createdLifePeer, 1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdLifePeer Context triple: [Alec Douglas-Home, createdLifePeer, 1974]
-
A.
createdPeer
Indicates that one entity brought another entity into existence or initiated its formation as a peer or counterpart.
-
B.
createdProcess
Indicates that an entity is responsible for originating or bringing into existence a particular process.
-
C.
lifePeerType
Indicates the specific category or rank of a life peer within a peerage or honors system.
-
D.
isLifePeer
chosen
Indicates that a person holds the title of life peer, having been granted a non-hereditary peerage (typically in the UK) that entitles them to sit in the upper legislative chamber.
-
E.
createdEarlBy
Indicates that an entity was granted or established as an earl by a specific creator or authority.
- 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.