Triple
T14238360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karamojong |
E352944
|
entity |
| Predicate | foodSecurityIssues |
P80394
|
FINISHED |
| Object | vulnerability to drought |
—
|
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: vulnerability to drought | Statement: [Karamojong, foodSecurityIssues, vulnerability to drought]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foodSecurityIssues Context triple: [Karamojong, foodSecurityIssues, vulnerability to drought]
-
A.
mainFoodAffected
Indicates that a primary or central food item is directly impacted or influenced by a specified action or condition.
-
B.
agriculturalDependence
Indicates that one entity relies on another for agricultural resources, production, or support.
-
C.
socialConcern
Indicates a relationship where an entity is concerned about, attentive to, or actively engaged with social issues, problems, or well-being.
-
D.
livelihoodVulnerability
chosen
Indicates the degree to which an entity’s means of making a living are exposed or susceptible to harm, disruption, or loss.
-
E.
secondaryFood
Indicates that one entity serves as a secondary or supplementary food source in relation to another entity.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62422e28819089e7115052a28c96 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.