Triple
T20575161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draghi Cabinet |
E505196
|
entity |
| Predicate | statusAfterResignation |
P140626
|
FINISHED |
| Object | caretaker government |
—
|
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: caretaker government | Statement: [Draghi Cabinet, statusAfterResignation, caretaker government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterResignation Context triple: [Draghi Cabinet, statusAfterResignation, caretaker government]
-
A.
titleAfterResignation
Indicates that the specified title is held by an entity after they have resigned from a previous position or role.
-
B.
statusAfterExile
Indicates the condition or standing an entity has once a period of exile has ended.
-
C.
acceptedResignationOf
Indicates that one entity formally agreed to and approved another entity’s decision to resign from a position or role.
-
D.
resignsTo
Indicates that one entity formally gives up a position, role, or claim in favor of or directed toward another entity or authority.
-
E.
canResign
Indicates that an entity has the authority or option to voluntarily leave a position, role, or membership.
- F. None of above. chosen
Provenance (4 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a909785c8190a02b1195eadb384c |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:39 a.m.