Triple
T29073589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Somerset |
E735873
|
entity |
| Predicate | laterCreationPeerage |
P85143
|
FINISHED |
| Object | Peerage of England |
—
|
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 England | Statement: [Dukes of Somerset, laterCreationPeerage, Peerage of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCreationPeerage Context triple: [Dukes of Somerset, laterCreationPeerage, Peerage of England]
-
A.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
B.
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.
-
C.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
D.
peerageCreationContext
Indicates the circumstances or setting in which a peerage title is established or conferred.
-
E.
peerageNumberOfCreations
chosen
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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 28, 2026, 10:21 a.m.