Triple
T12732085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary of the Angels Roman Catholic Church |
E304264
|
entity |
| Predicate | ecclesiasticalType |
P106619
|
FINISHED |
| Object | parish |
—
|
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 | Statement: [St Mary of the Angels Roman Catholic Church, ecclesiasticalType, parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecclesiasticalType Context triple: [St Mary of the Angels Roman Catholic Church, ecclesiasticalType, parish]
-
A.
ecclesiasticalLevel
Indicates the hierarchical rank or status of an entity within an ecclesiastical (church) organization.
-
B.
isEcclesiasticalFormOf
Indicates that one term is the ecclesiastical (church-related or liturgical) form or variant of another term.
-
C.
dioceseType
Indicates the specific ecclesiastical category or kind of diocese that an entity belongs to.
-
D.
ecclesiasticalStyle
Indicates the formal religious or clerical style or title by which an ecclesiastical person is properly addressed.
-
E.
ecclesiasticalOrientation
Indicates the religious or church-related affiliation, tendency, or alignment of an entity within an ecclesiastical context.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:25 p.m.