Triple
T851120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthodox Church of Alexandria |
E18386
|
entity |
| Predicate | scopeOfMission |
P13281
|
FINISHED |
| Object | pan-African |
—
|
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: pan-African | Statement: [Orthodox Church of Alexandria, scopeOfMission, pan-African]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfMission Context triple: [Orthodox Church of Alexandria, scopeOfMission, pan-African]
-
A.
missionScope
chosen
Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
-
B.
missionFocus
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
C.
missionProfile
Indicates the specific set of objectives, conditions, and operational parameters that define how a mission is planned, conducted, and evaluated.
-
D.
overseesMission
Indicates that one entity has responsibility for supervising, directing, or managing the execution of a mission undertaken by another entity.
-
E.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac22de288190913714d41e5a8e12 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.