Triple
T25876062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek Orthodox Archdiocese of Beirut and Byblos |
E651904
|
entity |
| Predicate | hasClericalRankOfHead |
P5046
|
FINISHED |
| Object | metropolitan |
—
|
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: metropolitan | Statement: [Greek Orthodox Archdiocese of Beirut and Byblos, hasClericalRankOfHead, metropolitan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClericalRankOfHead Context triple: [Greek Orthodox Archdiocese of Beirut and Byblos, hasClericalRankOfHead, metropolitan]
-
A.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
isEcclesiasticalHeadOf
Indicates that one entity serves as the highest religious or church authority for another entity.
-
C.
ecclesiasticalRank
chosen
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
D.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a diocese.
-
E.
hasClericalFunction
Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 22, 2026, 8:12 a.m.