Triple
T779031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian Orthodox Church |
E16454
|
entity |
| Predicate | clergyCelibacyRule |
P10287
|
FINISHED |
| Object | parish priests may be married |
—
|
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 priests may be married | Statement: [Romanian Orthodox Church, clergyCelibacyRule, parish priests may be married]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyCelibacyRule Context triple: [Romanian Orthodox Church, clergyCelibacyRule, parish priests may be married]
-
A.
clergyMayMarry
chosen
Indicates that members of the clergy are permitted to enter into marriage.
-
B.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
C.
clergyPractice
Indicates that a member of the clergy engages in, performs, or follows a particular religious practice or ritual.
-
D.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
E.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a90365648190ace53b0f0e87aa68 |
completed | March 1, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69a4a50bd23081908908235b8ec9201e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.