Triple
T32410794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Richard Kenrick |
E828213
|
entity |
| Predicate | appointedBishopOfStLouis |
P67420
|
FINISHED |
| Object | 1841 |
—
|
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: 1841 | Statement: [Peter Richard Kenrick, appointedBishopOfStLouis, 1841]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedBishopOfStLouis Context triple: [Peter Richard Kenrick, appointedBishopOfStLouis, 1841]
-
A.
appointedBishopOf
chosen
Indicates that a person has been officially assigned or consecrated to serve as the bishop responsible for a particular diocese or ecclesiastical jurisdiction.
-
B.
appointedBishopBy
Indicates that one entity was formally made a bishop through the authority or decision of another entity.
-
C.
appointedBishopOfRochesterBy
Indicates that one entity formally appointed another entity to the position of Bishop of Rochester.
-
D.
appointedBishopOfLondon
Indicates that a person was formally assigned or promoted to the position of Bishop of London.
-
E.
appointedAsArchbishop
Indicates that an authority formally assigned a person to hold the office or role of an archbishop.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 12:53 a.m.