Triple
T352269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Catholic Churches |
E7467
|
entity |
| Predicate | usesClericalDiscipline |
P1772
|
FINISHED |
| Object | married priesthood (in many churches) |
—
|
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: married priesthood (in many churches) | Statement: [Eastern Catholic Churches, usesClericalDiscipline, married priesthood (in many churches)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClericalDiscipline Context triple: [Eastern Catholic Churches, usesClericalDiscipline, married priesthood (in many churches)]
-
A.
hasClericalDiscipline
chosen
Indicates that an entity is subject to, or governed by, a particular set of clerical or religious disciplinary rules or practices.
-
B.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
C.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
D.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
-
E.
clergyPractice
Indicates that a member of the clergy engages in, performs, or follows a particular religious practice or ritual.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7f1be88190964ddcbb6a05f021 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.