Triple
T9494025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Axum |
E228960
|
entity |
| Predicate | hasEpiscopalRank |
P5046
|
FINISHED |
| Object | archbishop |
—
|
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: archbishop | Statement: [Archbishop of Axum, hasEpiscopalRank, archbishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpiscopalRank Context triple: [Archbishop of Axum, hasEpiscopalRank, archbishop]
-
A.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
ecclesiasticalRank
chosen
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
C.
hasSuffraganBishop
Indicates that one bishop holds the position of suffragan (subordinate or assistant) bishop in relation to another bishop or ecclesiastical authority.
-
D.
heldEcclesiasticalAuthorityIn
Indicates that an entity possessed official religious or church authority within a specified place or jurisdiction.
-
E.
hasEpiscopalArea
Indicates that one entity possesses or is assigned a specific episcopal jurisdiction or area of ecclesiastical authority over another.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95e8c8908190950e1130f9612823 |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.