Triple
T31303911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukedom of Cambridge |
E798281
|
entity |
| Predicate | previousCreationPeerage |
P164676
|
FINISHED |
| Object | Peerage of the United Kingdom |
—
|
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: Peerage of the United Kingdom | Statement: [Dukedom of Cambridge, previousCreationPeerage, Peerage of the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCreationPeerage Context triple: [Dukedom of Cambridge, previousCreationPeerage, Peerage of the United Kingdom]
-
A.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
B.
peerageCreationContext
chosen
Indicates the circumstances or setting in which a peerage title is established or conferred.
-
C.
linkedToPeerage
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
-
D.
laterPeerageConnections
Indicates that one entity acquires or forms peerage-related ties (such as titles, ranks, or noble associations) at a later time or stage in relation to another entity.
-
E.
peerageNumberOfCreations
Indicates the number of separate times a particular peerage title has been formally created.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 29, 2026, 9:14 p.m.