Triple
T28827206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPCUSA |
E727939
|
entity |
| Predicate | clergyGenderPolicy |
P89324
|
FINISHED |
| Object | men and women eligible for ordination |
—
|
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: men and women eligible for ordination | Statement: [UPCUSA, clergyGenderPolicy, men and women eligible for ordination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyGenderPolicy Context triple: [UPCUSA, clergyGenderPolicy, men and women eligible for ordination]
-
A.
priesthoodGender
Indicates the gender associated with a particular priesthood role or office.
-
B.
allowsOrdinationOfWomen
chosen
Indicates that an entity permits women to be formally ordained into official religious or clerical roles.
-
C.
clergyOrder
Indicates that an individual belongs to, or is formally associated with, a specific religious clerical order or denomination.
-
D.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
E.
clergyMayMarry
Indicates that members of the clergy are permitted to enter into marriage.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 6:36 a.m.