Triple
T10409947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian famine of 1601–1603 |
E245360
|
entity |
| Predicate | typeOfCrisis |
P93977
|
FINISHED |
| Object | food crisis |
—
|
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: food crisis | Statement: [Russian famine of 1601–1603, typeOfCrisis, food crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCrisis Context triple: [Russian famine of 1601–1603, typeOfCrisis, food crisis]
-
A.
typeOfCrisisManagement
Indicates the specific approach or method used to manage, respond to, or resolve a crisis situation.
-
B.
crisisRelatedTo
Indicates a relationship where one situation, event, or condition is connected to, associated with, or relevant to a crisis.
-
C.
crisisContext
Indicates that the relationship or action occurs within, is shaped by, or is specifically relevant to a crisis situation or emergency context.
-
D.
majorCrisis
Indicates a severe, high-impact crisis or emergency situation affecting an entity or system.
-
E.
notableDisasterType
Indicates the specific kind or category of disaster for which something (such as a place, event, or entity) is notable or best known.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9fb98748190a3a6c161edd8f400 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:09 p.m.