Triple
T27132198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convertibility Plan (Argentina) |
E681588
|
entity |
| Predicate | linkedCrisis |
P25894
|
FINISHED |
| Object | Argentine economic crisis of 2001–2002 |
—
|
NE NERFINISHED |
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: Argentine economic crisis of 2001–2002 | Statement: [Convertibility Plan (Argentina), linkedCrisis, Argentine economic crisis of 2001–2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedCrisis Context triple: [Convertibility Plan (Argentina), linkedCrisis, Argentine economic crisis of 2001–2002]
-
A.
crisisRelatedTo
chosen
Indicates a relationship where one situation, event, or condition is connected to, associated with, or relevant to a crisis.
-
B.
crisisAddressed
Indicates that an entity has taken action to respond to, manage, or resolve a specific crisis.
-
C.
viewOnCrises
Indicates a stance, opinion, or perspective that an entity holds regarding one or more crises.
-
D.
crisisManagement
Indicates the relationship in which an entity plans for, responds to, and mitigates the impact of disruptive or emergency situations.
-
E.
typeOfCrisis
Indicates the specific category or nature of a crisis that an entity is experiencing or associated with.
- 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_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 9:05 a.m.