Triple
T28786219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicholas Heath |
E726816
|
entity |
| Predicate | successorAsArchbishopOfYork |
P194984
|
FINISHED |
| Object | Thomas Young |
—
|
NE NERFINISHED |
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: Thomas Young | Statement: [Nicholas Heath, successorAsArchbishopOfYork, Thomas Young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsArchbishopOfYork Context triple: [Nicholas Heath, successorAsArchbishopOfYork, Thomas Young]
-
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.
precededInOfficeAsArchbishopOfWestminster
Indicates that one individual previously held the position of Archbishop of Westminster immediately before another individual.
-
D.
successorAsEarl
Indicates that one person became the next holder of the title of Earl after another person.
-
E.
appointedAsArchbishopOfWestminster
Indicates that a person has been formally appointed to hold the office of Archbishop of Westminster.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: April 28, 2026, 6:21 a.m.