Triple
T32476127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Declaration of Egregious Popish Impostures |
E829979
|
entity |
| Predicate | authorLaterOffice |
P151925
|
FINISHED |
| Object | Archbishop of York |
—
|
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: Archbishop of York | Statement: [A Declaration of Egregious Popish Impostures, authorLaterOffice, Archbishop of York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorLaterOffice Context triple: [A Declaration of Egregious Popish Impostures, authorLaterOffice, Archbishop of York]
-
A.
laterOffice
Indicates that one office or term of office occurs chronologically after another office or term.
-
B.
authorLaterBecame
chosen
Indicates that the subject, who is an author of something, subsequently took on or transitioned into the role or status specified by the object at a later time.
-
C.
namedAfterWorkAuthor
Indicates that an entity is named after the author of a particular work.
-
D.
afterOffice
Indicates that one event, action, or state occurs after the end of normal office or working hours.
-
E.
authorOfPreviousWork
Indicates that one entity is the creator or writer of an earlier work referenced or built upon by another entity.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 12:58 a.m.