Triple
T8525178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Hodge Gresford Jones |
E201795
|
entity |
| Predicate | clericalStyle |
P13126
|
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: [Henry Hodge Gresford Jones, clericalStyle, The Right Reverend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clericalStyle Context triple: [Henry Hodge Gresford Jones, clericalStyle, The Right Reverend]
-
A.
officeStyle
Indicates a stylistic or design relationship where one entity’s style is characterized as “office” or suitable for an office environment.
-
B.
styleFamily
Indicates that one style is grouped within the same stylistic family or category as another style.
-
C.
calligraphicUse
Indicates that one entity uses or applies another entity specifically for calligraphic purposes or in the practice of calligraphy.
-
D.
ecclesiasticalStyle
chosen
Indicates the formal religious or clerical style or title by which an ecclesiastical person is properly addressed.
-
E.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe644c4648190a14dcaeaa90d72c7 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.