Triple
T30986441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic papal selection process of 2012 |
E789539
|
entity |
| Predicate | selectedOffice |
P157688
|
FINISHED |
| Object | Pope of Alexandria |
—
|
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: Pope of Alexandria | Statement: [Coptic papal selection process of 2012, selectedOffice, Pope of Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedOffice Context triple: [Coptic papal selection process of 2012, selectedOffice, Pope of Alexandria]
-
A.
officeChosen
chosen
Indicates that a particular office has been selected or designated from among available options.
-
B.
subjectOffice
Indicates the office or official position held by the subject in relation to another entity or context.
-
C.
specifiesOffice
Indicates that an entity is assigned to or associated with a particular office or official position.
-
D.
targetedOffice
Indicates that an action, event, or campaign was specifically directed at or focused on a particular office or organizational unit.
-
E.
givenByOffice
Indicates that something (such as a document, decision, or service) is provided or issued by a specific office or official authority.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 8:56 p.m.