Triple
T25390273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicolás Salmerón y Alonso |
E636144
|
entity |
| Predicate | mannerOfLeavingOffice |
P90163
|
FINISHED |
| Object | resignation |
—
|
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 | Statement: [Nicolás Salmerón y Alonso, mannerOfLeavingOffice, resignation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mannerOfLeavingOffice Context triple: [Nicolás Salmerón y Alonso, mannerOfLeavingOffice, resignation]
-
A.
methodOfRemovalFromOffice
chosen
Indicates the specific process or procedure by which an officeholder is removed from their position.
-
B.
presidentAtEndOfTerm
Indicates that the subject held the office of president at the conclusion of a specified term or period.
-
C.
afterLeavingOffice
Indicates that one event, action, or state occurs subsequent to an entity’s departure from an official position or office.
-
D.
endOfPresidencyEvent
Indicates the event or point in time at which a presidency formally concludes.
-
E.
officeHoldersTerminatedBy
Indicates that an office holder’s term in a position ended as a result of an action taken by a specified terminating agent (such as a person, body, or authority).
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5656e488c8190bf5c00f69ae165fc |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:49 p.m.