Triple
T25606235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antipope Felix II |
E641920
|
entity |
| Predicate | successorClaimed |
P133902
|
FINISHED |
| Object | Pope Damasus I |
—
|
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 Damasus I | Statement: [Antipope Felix II, successorClaimed, Pope Damasus I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorClaimed Context triple: [Antipope Felix II, successorClaimed, Pope Damasus I]
-
A.
successorStateClaimedBy
Indicates that a particular state asserts itself as the legal or political successor to another state.
-
B.
successorClaimant
chosen
Indicates that one entity is the next or replacement claimant to a right, title, or claim previously held by another entity.
-
C.
attemptedToAppointAsSuccessor
Indicates that one entity tried, but did not necessarily succeed, to designate another entity as its successor.
-
D.
successorDesignated
Indicates that one entity has been formally chosen or named to take over the role, position, or responsibilities of another entity in the future.
-
E.
claimPassedTo
Indicates that a claim has been transferred from one party or system to another, typically for further processing, ownership, or responsibility.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 4:38 p.m.