Triple
T32034614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignatius Aphrem II |
E818057
|
entity |
| Predicate | episcopalName |
P173143
|
FINISHED |
| Object | Aphrem |
—
|
NE NERFINISHED |
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: Aphrem | Statement: [Ignatius Aphrem II, episcopalName, Aphrem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: episcopalName Context triple: [Ignatius Aphrem II, episcopalName, Aphrem]
-
A.
episcopalCharacter
Indicates that an entity possesses the status, authority, or qualities associated with a bishop within an ecclesiastical hierarchy.
-
B.
usesEpiscopalTitle
Indicates that one entity refers to or addresses another entity using an official episcopal (bishop-related) title.
-
C.
isNonEpiscopalTitle
Indicates that a given title does not belong to or derive from an episcopal (bishop-related) office or rank.
-
D.
episcopalSeeOf
Indicates that one entity serves as the episcopal see (the official seat or jurisdictional center) of a bishop or similar ecclesiastical authority for another entity.
-
E.
episcopalInsignia
Indicates the relationship in which certain items or symbols serve as the official insignia associated with a bishop’s ecclesiastical office or authority.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49a18748190bfc7061da3eebef6 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:18 a.m.