Triple
T18410927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monti government |
E441753
|
entity |
| Predicate | resignationEffective |
P6919
|
FINISHED |
| Object | 2012-12-21 |
—
|
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: 2012-12-21 | Statement: [Monti government, resignationEffective, 2012-12-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resignationEffective Context triple: [Monti government, resignationEffective, 2012-12-21]
-
A.
acceptedResignationOf
Indicates that one entity formally agreed to and approved another entity’s decision to resign from a position or role.
-
B.
resignsTo
Indicates that one entity formally gives up a position, role, or claim in favor of or directed toward another entity or authority.
-
C.
canResign
Indicates that an entity has the authority or option to voluntarily leave a position, role, or membership.
-
D.
canResignTo
Indicates that one party has the ability or permission to formally resign their position, role, or membership to another designated party or authority.
-
E.
resignationDateOfRespondent
chosen
Indicates the date on which the respondent formally resigned from their position or role.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5195df3288190be61f4053476c735 |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.