Triple
T30078121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Antigonish |
E764379
|
entity |
| Predicate | officeCreationAuthority |
P196498
|
FINISHED |
| Object | Holy See |
—
|
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: Holy See | Statement: [Bishop of Antigonish, officeCreationAuthority, Holy See]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeCreationAuthority Context triple: [Bishop of Antigonish, officeCreationAuthority, Holy See]
-
A.
signatoryAuthority
Indicates that an entity has the legal power or authorization to sign documents or agreements on behalf of another party.
-
B.
signatoryOffice
Indicates the office or organizational unit that formally signs or authorizes a document, agreement, or record.
-
C.
officeCreatedFor
Indicates that an office or position was established specifically to serve, represent, or support a particular entity.
-
D.
signatoryOrganization
Indicates that an organization has formally signed or endorsed an agreement, document, or commitment.
-
E.
issuerOffice
Indicates the office or organizational unit that formally issues or authorizes something (such as a document, credential, or statement).
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: April 29, 2026, 7:02 p.m.