Triple

T23904977
Position Surface form Disambiguated ID Type / Status
Subject Archdeacon of Exeter E601165 entity
Predicate officeHoldersInclude P537 FINISHED
Object John Satterthwaite
John Satterthwaite was an Anglican clergyman who served in senior ecclesiastical leadership, including the role of Archdeacon of Exeter.
E1625490 NE 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: John Satterthwaite | Statement: [Archdeacon of Exeter, officeHoldersInclude, John Satterthwaite]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: John Satterthwaite
Triple: [Archdeacon of Exeter, officeHoldersInclude, John Satterthwaite]
Generated description
John Satterthwaite was an Anglican clergyman who served in senior ecclesiastical leadership, including the role of Archdeacon of Exeter.

Provenance (5 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_69e295364a488190bcac702e9bb7f764 completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1cde13e88819086bbd0bc4a5b6a36 completed April 29, 2026, 9:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fbceec9f48190a61c9f9c1d3747b1 completed May 22, 2026, 2:18 a.m.
NEDg Description generation batch_6a0fbe78822881909e04f037a60db091 completed May 22, 2026, 2:24 a.m.
NED2 Entity disambiguation (via description) batch_6a0fbf0ed7808190b64797da02f8fbac completed May 22, 2026, 2:27 a.m.
Created at: April 17, 2026, 8:26 p.m.