Triple
T262883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Catholicism |
E5787
|
entity |
| Predicate | clergyPractice |
P9352
|
FINISHED |
| Object | ordination of married men to the priesthood |
—
|
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: ordination of married men to the priesthood | Statement: [Old Catholicism, clergyPractice, ordination of married men to the priesthood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyPractice Context triple: [Old Catholicism, clergyPractice, ordination of married men to the priesthood]
-
A.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
B.
churchOrder
Indicates the hierarchical or organizational structure that defines roles, authority, and governance within a church or religious institution.
-
C.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
D.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
E.
hasClericalDiscipline
Indicates that an entity is subject to, or governed by, a particular set of clerical or religious disciplinary rules or practices.
- 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_69a258dd8ea08190ac554a1cc8dfd8c3 |
completed | Feb. 28, 2026, 2:54 a.m. |
| NER | Named-entity recognition | batch_69a25d8c7f448190af9145256f994177 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25d0ec71081908478c800be4f7bb0 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.