Triple
T1254835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priestly Fraternity of Saint Peter |
E26962
|
entity |
| Predicate | typeOfApostolate |
P12785
|
FINISHED |
| Object | parish ministry |
—
|
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: parish ministry | Statement: [Priestly Fraternity of Saint Peter, typeOfApostolate, parish ministry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfApostolate Context triple: [Priestly Fraternity of Saint Peter, typeOfApostolate, parish ministry]
-
A.
apostolate
chosen
Indicates the relationship in which an individual or group carries out a mission of religious or spiritual outreach, service, or evangelization on behalf of a faith community.
-
B.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
C.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
D.
vocationType
Indicates the specific kind or category of occupation, profession, or calling associated with an entity.
-
E.
theologicalRole
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bfa5a4cc819093ed686619b572d8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.