Triple
T19106371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffragan Bishops Act 1534 |
E467666
|
entity |
| Predicate | authorizesOffice |
P83676
|
FINISHED |
| Object | suffragan bishop |
—
|
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: suffragan bishop | Statement: [Suffragan Bishops Act 1534, authorizesOffice, suffragan bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizesOffice Context triple: [Suffragan Bishops Act 1534, authorizesOffice, suffragan bishop]
-
A.
givenByOffice
Indicates that something (such as a document, decision, or service) is provided or issued by a specific office or official authority.
-
B.
governingOffice
Indicates the official position or office through which an entity exercises governing authority over a jurisdiction or organization.
-
C.
officeGrantedFor
chosen
Indicates that an official position or role has been formally conferred upon an entity for a specified purpose, term, or context.
-
D.
advisedOffice
Indicates that one entity has provided guidance or recommendations to an office or organizational unit.
-
E.
isOfficialOfficeOf
Indicates that one entity serves as the formally recognized office or headquarters associated with 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e37159688190a6896d9730214ba8 |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.