Triple
T10824479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Spencer, 3rd Duke of Marlborough |
E255458
|
entity |
| Predicate | heldPeerageFrom |
P1913
|
FINISHED |
| Object | 1733 |
—
|
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: 1733 | Statement: [Charles Spencer, 3rd Duke of Marlborough, heldPeerageFrom, 1733]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldPeerageFrom Context triple: [Charles Spencer, 3rd Duke of Marlborough, heldPeerageFrom, 1733]
-
A.
elevatedToPeerageFor
Indicates that a person was granted a noble title or peerage specifically as a result of, or in recognition for, a particular reason, action, or service.
-
B.
linkedToPeerage
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
-
C.
conveysPeerage
Indicates that one entity formally grants or transfers a noble title or rank of peerage to another entity.
-
D.
hereditaryPeerage
chosen
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
E.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734cf7918819094d36ea208c80d12 |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.