Triple
T5455303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felix V |
E122463
|
entity |
| Predicate | successorAsAntipope |
P64139
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Felix V, successorAsAntipope, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsAntipope Context triple: [Felix V, successorAsAntipope, none]
-
A.
successorAsImperialAntipope
Indicates that one entity became the next imperial antipope following another in a succession.
-
B.
predecessorAsImperialAntipope
Indicates that one entity served immediately before another in the specific role of imperial antipope.
-
C.
enthronedAsAntipope
Indicates that a person has been installed or recognized as an antipope, claiming the papal office in opposition to the legitimate pope.
-
D.
electedAsAntipope
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.
-
E.
resignedAsAntipopeInFavorOf
Indicates that an individual who had claimed the papacy as an antipope stepped down from that claim in order to recognize and support another pope instead.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a0d96c8190bd1299edbf764bbb |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd927b0b4c81909d5e0f594822e3f9 |
completed | March 20, 2026, 6:31 p.m. |
Created at: March 20, 2026, 2:08 p.m.