Triple
T33633724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine rite |
E861633
|
entity |
| Predicate | hasPrimaryClericalOrder |
—
|
GENERATED |
| Object | bishop |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryClericalOrder Context triple: [Byzantine rite, hasPrimaryClericalOrder, bishop]
-
A.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
-
B.
hasClergyOrder
chosen
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
C.
hasClericalAssociation
Indicates a relationship in which an entity is connected to or involved with clerical roles, duties, or religious office.
-
D.
hasClericalState
Indicates that an entity possesses or is associated with a particular clerical or administrative status or condition.
-
E.
hasClericalMember
Indicates that an entity includes or is associated with a member who performs clerical or administrative duties.
- F. None of above.
Provenance (1 batch)
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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.