Triple
T15696344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papal conclave of 1555 |
E380468
|
entity |
| Predicate | electeeDeath |
P22489
|
FINISHED |
| Object | May 1, 1555 |
—
|
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: May 1, 1555 | Statement: [Papal conclave of 1555, electeeDeath, May 1, 1555]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electeeDeath Context triple: [Papal conclave of 1555, electeeDeath, May 1, 1555]
-
A.
hasDeceasedParent
Indicates that an entity has at least one parent who is no longer living.
-
B.
deathDateEvent
chosen
Indicates the date on which a death occurred or a death-related event took place.
-
C.
signedBeforeDeathOf
Indicates that one entity signed something at a time earlier than the death of another specified entity.
-
D.
associatedWithDeathOf
Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
-
E.
firstHolderDeathDate
Indicates the date on which the initial or original holder of something (such as a title, account, or asset) died.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.