Triple
T25760789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign Priest |
E648733
|
entity |
| Predicate | isNonEpiscopalTitle |
P162114
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sovereign Priest, isNonEpiscopalTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonEpiscopalTitle Context triple: [Sovereign Priest, isNonEpiscopalTitle, true]
-
A.
isEcclesiasticalTitle
Indicates that the entity functions as a formal religious or church office, rank, or honorific title within an ecclesiastical context.
-
B.
usesEpiscopalTitle
Indicates that one entity refers to or addresses another entity using an official episcopal (bishop-related) title.
-
C.
ecclesiasticalTitleIncludes
Indicates that one ecclesiastical title contains, subsumes, or incorporates another ecclesiastical title as part of its designation or scope.
-
D.
usesArchiepiscopalTitle
Indicates that an entity employs an archiepiscopal (archbishop-level) ecclesiastical title in its official style or designation.
-
E.
isTitularChurchTitleOf
Indicates that a given church serves as the official titular church associated with a particular cardinal’s title.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 22, 2026, 5:05 a.m.