Triple
T5670581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Ripon |
E124964
|
entity |
| Predicate | dateOfFirstBishopConsecration |
P65892
|
FINISHED |
| Object | 1836 |
—
|
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: 1836 | Statement: [Diocese of Ripon, dateOfFirstBishopConsecration, 1836]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstBishopConsecration Context triple: [Diocese of Ripon, dateOfFirstBishopConsecration, 1836]
-
A.
firstBishop
Indicates that one entity is the first bishop (earliest in time or rank) associated with or holding episcopal authority over another entity.
-
B.
startTimeOfEpiscopate
Indicates the date and time when a person's period of serving as a bishop (episcopate) begins.
-
C.
firstDiocesanBishopEndOfOffice
Indicates the point in time or event at which the first diocesan bishop’s term of office comes to an end.
-
D.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
E.
currentArchbishopStartYear
Indicates the calendar year in which the current archbishop began serving in that role.
- F. None of above. chosen
Provenance (4 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c0252e18988190a8f3aa0684c12fb8 |
completed | March 22, 2026, 5:21 p.m. |
Created at: March 22, 2026, 3:43 p.m.