Triple
T37384594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Sharp |
E928531
|
entity |
| Predicate | appointedAsArchbishopOfYorkInYear |
P67839
|
FINISHED |
| Object | 1691 |
—
|
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: 1691 | Statement: [John Sharp, appointedAsArchbishopOfYorkInYear, 1691]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsArchbishopOfYorkInYear Context triple: [John Sharp, appointedAsArchbishopOfYorkInYear, 1691]
-
A.
appointedAsArchbishopOfYork
Indicates that a person has been formally appointed to serve in the role of Archbishop of York.
-
B.
servedAsArchbishopOfYorkUntil
Indicates having held the position of Archbishop of York up to a specified end date or point in time.
-
C.
officeStartAsArchbishopOfYork
chosen
Indicates the point in time when an individual begins serving in the role of Archbishop of York.
-
D.
appointedAsBishopOfDurhamBy
Indicates that one entity formally appointed another entity to the position of Bishop of Durham.
-
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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:16 p.m.