Triple
T13943883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Fenwick |
E335328
|
entity |
| Predicate | clericalTitle |
P2097
|
FINISHED |
| Object | The Right Reverend |
—
|
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 Reverend | Statement: [Richard Fenwick, clericalTitle, The Right Reverend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clericalTitle Context triple: [Richard Fenwick, clericalTitle, The Right Reverend]
-
A.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
-
B.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
C.
governmentOfficeOrTitleOf
Indicates that one entity is a government office or official title held by, associated with, or designating the role of another entity.
-
D.
typicalOfficeHolderTitle
Indicates the standard or commonly used title typically held by the office holder of a given position or role.
-
E.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e0f6f3c8190a64058b732b0ac52 |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.