Triple
T17998918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camillo Pamphilj |
E430572
|
entity |
| Predicate | reasonForEndOfCardinalate |
P54944
|
FINISHED |
| Object | resignation to marry |
—
|
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: resignation to marry | Statement: [Camillo Pamphilj, reasonForEndOfCardinalate, resignation to marry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEndOfCardinalate Context triple: [Camillo Pamphilj, reasonForEndOfCardinalate, resignation to marry]
-
A.
redeemabilityEndedReason
Indicates the reason why the ability to redeem something (e.g., a product, offer, or asset) has ended.
-
B.
reasonForEndOfRule
chosen
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
-
C.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
-
D.
reasonForAnnulment
Indicates the specific cause or grounds on which a prior decision, agreement, or status is formally annulled or declared invalid.
-
E.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e6a2a881908af2d0a4a5053916 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.