Triple
T27132247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernando de la Rúa |
E681589
|
entity |
| Predicate | methodOfLeavingOffice |
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: [Fernando de la Rúa, methodOfLeavingOffice, resignation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfLeavingOffice Context triple: [Fernando de la Rúa, methodOfLeavingOffice, 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.
termLimitReasonForLeavingOffice
Indicates that an officeholder left their position specifically because they reached a legally or formally imposed term limit.
-
D.
endOfPresidencyEvent
Indicates the event or point in time at which a presidency formally concludes.
-
E.
retiredFromPresidentialService
Indicates that an individual has concluded and formally ended their period of service in a presidential role or office.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:05 a.m.