Triple
T5455299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felix V |
E122463
|
entity |
| Predicate | electionAsAntipopeDate |
P18969
|
FINISHED |
| Object | 1439-11-05 |
—
|
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: 1439-11-05 | Statement: [Felix V, electionAsAntipopeDate, 1439-11-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionAsAntipopeDate Context triple: [Felix V, electionAsAntipopeDate, 1439-11-05]
-
A.
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.
-
B.
papalElectionDate
chosen
Indicates the date on which a pope was formally elected to the papacy.
-
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.
chronologicalOrderAsAntipope
Indicates that one entity is positioned before or after another in the historical sequence of individuals recognized as antipopes.
-
E.
endTimeAsAntipope
Indicates the point in time at which an individual’s status or role as an antipope comes to an end.
- 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_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. |
Created at: March 20, 2026, 2:08 p.m.