Triple
T3857868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sede vacante |
E90061
|
entity |
| Predicate | suspendsOffice |
P41676
|
FINISHED |
| Object | papal office |
—
|
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: papal office | Statement: [sede vacante, suspendsOffice, papal office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspendsOffice Context triple: [sede vacante, suspendsOffice, papal office]
-
A.
officeSuspendedUnder
chosen
Indicates that an individual’s official position or duties are temporarily halted under the authority or jurisdiction of a specified entity or rule.
-
B.
suspendedIn
Indicates that one entity is held or maintained within another medium or environment without settling or separating.
-
C.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
D.
heldExOfficioBy
Indicates that a position, office, or role is occupied by someone by virtue of holding another office or status, rather than by separate appointment or election.
-
E.
succeedsFromOffice
Indicates that one officeholder directly follows another in holding the same office or position.
- 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.