Triple
T28726993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23rd Earl of Derby |
E730250
|
entity |
| Predicate | holderHonorificPrefix |
P368
|
FINISHED |
| Object | The Right Honourable |
—
|
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: The Right Honourable | Statement: [23rd Earl of Derby, holderHonorificPrefix, The Right Honourable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderHonorificPrefix Context triple: [23rd Earl of Derby, holderHonorificPrefix, The Right Honourable]
-
A.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
-
B.
honoraryPrefix
Indicates that one entity serves as an honorific title or respectful prefix attached to the name of another entity.
-
C.
hasHonorificPrefix
chosen
Indicates that one entity is used as an honorific title or prefix attached to another entity’s name.
-
D.
honorificPartOfName
Indicates that an honorific title or form of address is included as part of a person's full name.
-
E.
honorificInitial
Indicates that one entity is the initial letter or abbreviated form of an honorific title used for another entity.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:56 a.m.