Triple
T3857883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sede vacante |
E90061
|
entity |
| Predicate | causesCessationOfOffice |
P34754
|
FINISHED |
| Object | most heads of Roman Curia |
—
|
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: most heads of Roman Curia | Statement: [sede vacante, causesCessationOfOffice, most heads of Roman Curia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causesCessationOfOffice Context triple: [sede vacante, causesCessationOfOffice, most heads of Roman Curia]
-
A.
causeOfEndOfPresidency
chosen
Indicates the event, action, or circumstance that directly led to the termination of a person’s presidency.
-
B.
succeedsFromOffice
Indicates that one officeholder directly follows another in holding the same office or position.
-
C.
losesElectionFor
Indicates that one candidate is defeated by another candidate in a specific election for a particular office or position.
-
D.
officeHoldersMustNot
Indicates that certain individuals are prohibited from holding specified offices or positions.
-
E.
termEndAsLeaderOfOpposition
Indicates the point in time when an entity’s tenure serving as leader of the opposition 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec1e68f88190941c39221486f6ae |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.