Triple
T18746561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | apostolic protonotaries |
E458420
|
entity |
| Predicate | clericalState |
P119519
|
FINISHED |
| Object | usually diocesan priests |
—
|
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: usually diocesan priests | Statement: [apostolic protonotaries, clericalState, usually diocesan priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clericalState Context triple: [apostolic protonotaries, clericalState, usually diocesan priests]
-
A.
hasClericalState
chosen
Indicates that an entity possesses or is associated with a particular clerical or administrative status or condition.
-
B.
officeState
Indicates the current operational or functional status of an office (e.g., open, closed, active, inactive) at a given time.
-
C.
clericalBranchOf
Indicates that one entity functions as an administrative or clerical subdivision or office that is part of another, larger organizational entity.
-
D.
signatoryState
Indicates that a state is a formal party to, and has signed or ratified, a specific treaty, agreement, or legal instrument.
-
E.
notableOfficeStatus
Indicates that an entity holds or has held a particularly significant or distinguished official position or office.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e576936cf08190b3c0d2f4e8a616fc |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.