Triple
T9260729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuer |
E222569
|
entity |
| Predicate | livelihoodRisk |
P80394
|
FINISHED |
| Object | vulnerability to flooding |
—
|
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 flooding | Statement: [Nuer, livelihoodRisk, vulnerability to flooding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livelihoodRisk Context triple: [Nuer, livelihoodRisk, vulnerability to flooding]
-
A.
livelihoodVulnerability
chosen
Indicates the degree to which an entity’s means of making a living are exposed or susceptible to harm, disruption, or loss.
-
B.
livelihood
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
C.
livelihoodChange
Indicates a change in a person’s or group’s means of making a living, such as improvements, declines, or shifts in income-generating activities.
-
D.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
E.
hasNaturalHazardRisk
Indicates that an entity is exposed or subject to potential damage or impact from one or more natural hazards (e.g., earthquakes, floods, storms).
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07175be881908a917573ec9b9081 |
completed | April 1, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:32 p.m.