Triple
T16843387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Archer of Weston-super-Mare |
E409468
|
entity |
| Predicate | lifePeerage |
P37952
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Baron Archer of Weston-super-Mare, lifePeerage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifePeerage Context triple: [Baron Archer of Weston-super-Mare, lifePeerage, true]
-
A.
peerageForLife
chosen
Indicates that an individual holds a noble title or rank granted for the duration of their lifetime only, without hereditary succession.
-
B.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
C.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
-
D.
linkedToPeerage
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
-
E.
typeOfPeerage
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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b35284588190a1d6238438f3e70d |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.