Triple
T19711727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron MacGregor of Pulham Market |
E473363
|
entity |
| Predicate | titleHolderHonorificPrefix |
P536
|
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: [Baron MacGregor of Pulham Market, titleHolderHonorificPrefix, The Right Honourable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderHonorificPrefix Context triple: [Baron MacGregor of Pulham Market, titleHolderHonorificPrefix, The Right Honourable]
-
A.
honorificPrefix
chosen
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.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
D.
hasHonorificPrefix
Indicates that one entity is used as an honorific title or prefix attached to another entity’s name.
-
E.
honorificTitleGivenBy
Indicates that an honorific title is formally conferred on one entity by 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64408bde08190aa3bef8516491e03 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.