Triple
T37384595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Sharp |
E928531
|
entity |
| Predicate | servedAsArchbishopOfYorkUntilYear |
P91142
|
FINISHED |
| Object | 1714 |
—
|
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: 1714 | Statement: [John Sharp, servedAsArchbishopOfYorkUntilYear, 1714]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsArchbishopOfYorkUntilYear Context triple: [John Sharp, servedAsArchbishopOfYorkUntilYear, 1714]
-
A.
servedAsArchbishopOfYorkUntil
chosen
Indicates having held the position of Archbishop of York up to a specified end date or point in time.
-
B.
servedAsArchbishopOfStAndrewsUntil
Indicates that a person held the position of Archbishop of St Andrews up to a specified end date or time.
-
C.
appointedAsArchbishopOfYork
Indicates that a person has been formally appointed to serve in the role of Archbishop of York.
-
D.
successorAsArchbishopOfYork
Indicates that one individual became the next Archbishop of York following another individual in that ecclesiastical office.
-
E.
servedAsArchbishopOfGlasgowUntil
Indicates that a person held the position of Archbishop of Glasgow up to a specified end date or year.
- 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_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 3, 2026, 4:16 p.m.