Triple
T1472216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute of Christ the King Sovereign Priest |
E27159
|
entity |
| Predicate | clericalMembers |
P9815
|
FINISHED |
| Object | 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: priests | Statement: [Institute of Christ the King Sovereign Priest, clericalMembers, priests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clericalMembers Context triple: [Institute of Christ the King Sovereign Priest, clericalMembers, priests]
-
A.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
B.
personnelComposition
Indicates the makeup or distribution of people or roles within a group, organization, or unit.
-
C.
hasClergy
chosen
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
electedMembers
Indicates that certain individuals have been chosen through an election process to serve as members of a specific body or organization.
-
E.
ecclesiasticalRank
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5dc90e481908a4935f266bc7850 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.