Triple
T33633724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine rite |
E861633
|
entity |
| Predicate | hasPrimaryClericalOrder |
P3105
|
FINISHED |
| Object | bishop |
—
|
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: bishop | Statement: [Byzantine rite, hasPrimaryClericalOrder, bishop]
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 (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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01b241f7308190bedb7522cb5dc069 |
completed | May 11, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a01b19ff12c81908ee1b188b4a3e118 |
completed | May 11, 2026, 10:38 a.m. |
Created at: May 1, 2026, 1:41 a.m.