Triple
T2049690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopian Orthodox Tewahedo Church |
E45535
|
entity |
| Predicate | clergyOrders |
P3105
|
FINISHED |
| Object | deacons |
—
|
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: deacons | Statement: [Ethiopian Orthodox Tewahedo Church, clergyOrders, deacons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clergyOrders Context triple: [Ethiopian Orthodox Tewahedo Church, clergyOrders, deacons]
-
A.
hasClergyOrder
chosen
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
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.
churchOrder
Indicates the hierarchical or organizational structure that defines roles, authority, and governance within a church or religious institution.
-
E.
religiousAdministration
Indicates that one entity holds authority or responsibility for managing, overseeing, or governing the religious affairs, practices, or institutions of another entity.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98e10d48190bb96cd1f8ea3c08b |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.