Triple
T30986440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic papal selection process of 2012 |
E789539
|
entity |
| Predicate | selectedPerson |
P2308
|
FINISHED |
| Object | Tawadros II 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: Tawadros II of Alexandria | Statement: [Coptic papal selection process of 2012, selectedPerson, Tawadros II of Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedPerson Context triple: [Coptic papal selection process of 2012, selectedPerson, Tawadros II of Alexandria]
-
A.
hasPerson
chosen
Indicates that an entity is associated with or includes a specific person.
-
B.
namedIndividual
Indicates that the subject is a specific, uniquely identified individual entity rather than a general class or type.
-
C.
servedPerson
Indicates that one entity has provided service, assistance, or attention to another entity.
-
D.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
E.
metPerson
Indicates that one person has encountered or come into contact with another person, typically in a face-to-face meeting.
- 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_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:56 p.m.