Triple
T4403095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Orthodox Church |
E93661
|
entity |
| Predicate | clergyCanMarryAfterOrdination |
P10287
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Polish Orthodox Church, clergyCanMarryAfterOrdination, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyCanMarryAfterOrdination Context triple: [Polish Orthodox Church, clergyCanMarryAfterOrdination, no]
-
A.
clergyMayMarry
chosen
Indicates that members of the clergy are permitted to enter into marriage.
-
B.
clergyOrder
Indicates that an individual belongs to, or is formally associated with, a specific religious clerical order or denomination.
-
C.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
D.
allowedOrdinationOf
Indicates that one entity permits or authorizes the formal religious ordination of another entity.
-
E.
wasOrdainedAs
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d08a0c8190ac6c125df40eca75 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.