Triple
T36839455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guido di Crema |
E910363
|
entity |
| Predicate | electionAsAntipope |
P49006
|
FINISHED |
| Object | 1164 |
—
|
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: 1164 | Statement: [Guido di Crema, electionAsAntipope, 1164]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionAsAntipope Context triple: [Guido di Crema, electionAsAntipope, 1164]
-
A.
electedAsAntipope
chosen
Indicates that an individual has been chosen or proclaimed as an antipope, i.e., a rival claimant to the papacy in opposition to the recognized pope.
-
B.
enthronedAsAntipope
Indicates that a person has been installed or recognized as an antipope, claiming the papal office in opposition to the legitimate pope.
-
C.
successorAsAntipope
Indicates that one individual assumed the role of antipope directly after another, succeeding them in that contested papal position.
-
D.
papalElection
Indicates the process or event in which a new pope is chosen and formally elected to the papal office.
-
E.
declaredAntipopeBy
Indicates that one entity formally proclaimed another entity to be an antipope, i.e., a rival claimant to the papacy opposed to the recognized pope.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.