Triple
T25606234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antipope Felix II |
E641920
|
entity |
| Predicate | predecessorClaimed |
P21282
|
FINISHED |
| Object | Pope Liberius |
—
|
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 Liberius | Statement: [Antipope Felix II, predecessorClaimed, Pope Liberius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorClaimed Context triple: [Antipope Felix II, predecessorClaimed, Pope Liberius]
-
A.
predecessorAsClaimant
chosen
Indicates that one entity previously held the status or role of claimant before another entity in a succession or sequence of claims.
-
B.
successorStateClaimedBy
Indicates that a particular state asserts itself as the legal or political successor to another state.
-
C.
ownedByPredecessor
Indicates that something is or was owned by an entity that previously held a given role, position, or status before the current one.
-
D.
predecessorStatus
Indicates that one entity’s status is determined by, or directly follows from, the status of a preceding entity in a sequence or process.
-
E.
predecessorUsedUntil
Indicates that an earlier version or predecessor of an entity remained in use up to a specified time or event.
- 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_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 4:38 p.m.