Triple
T19290794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Baker |
E482433
|
entity |
| Predicate | appointedAsBishopOfFulham |
P67420
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Jonathan Baker, appointedAsBishopOfFulham, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsBishopOfFulham Context triple: [Jonathan Baker, appointedAsBishopOfFulham, 2013]
-
A.
appointedBishopOfLondon
Indicates that a person was formally assigned or promoted to the position of Bishop of London.
-
B.
appointedBishopOfWinchester
Indicates that a person was formally appointed to serve as the Bishop of Winchester.
-
C.
appointedAsArchbishopOfWestminster
Indicates that a person has been formally appointed to hold the office of Archbishop of Westminster.
-
D.
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.
-
E.
appointedAsArchbishopOfWestminsterBy
Indicates that one entity formally selected and installed another entity into the position of Archbishop of Westminster.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc05c9dc8190846b279f82ae0fa3 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.