Triple
T8277480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Youssef Absi |
E193581
|
entity |
| Predicate | leadsChurchOfByzantineTradition |
P82454
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Youssef Absi, leadsChurchOfByzantineTradition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadsChurchOfByzantineTradition Context triple: [Youssef Absi, leadsChurchOfByzantineTradition, true]
-
A.
typeInByzantineRite
Indicates that an entity is classified or designated as following the Byzantine Rite.
-
B.
canonicalStatusInEasternOrthodoxChurch
Indicates whether something is recognized as canonically valid or legitimate within the Eastern Orthodox Church.
-
C.
canonicalStatusInOrientalOrthodoxChurches
Indicates whether something is recognized as canonically valid or legitimate within the Oriental Orthodox Churches.
-
D.
inEasternOrthodoxyPractice
Indicates that an action, belief, or practice occurs within, follows, or is characteristic of Eastern Orthodox religious practice.
-
E.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
- F. None of above. chosen
Provenance (4 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ea3fb481908b59414702a5147e |
completed | March 31, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:51 p.m.