Triple
T27147839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mro |
E681997
|
entity |
| Predicate | livelihoodChallenges |
P161906
|
FINISHED |
| Object | deforestation |
—
|
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: deforestation | Statement: [Mro, livelihoodChallenges, deforestation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livelihoodChallenges Context triple: [Mro, livelihoodChallenges, deforestation]
-
A.
livelihoodChallenges
chosen
Indicates difficulties or obstacles that negatively affect an entity’s ability to secure or maintain its means of living or income.
-
B.
livelihoodVulnerability
Indicates the degree to which an entity’s means of making a living are exposed or susceptible to harm, disruption, or loss.
-
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.
livelihood
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
E.
hasAgriculturalChallenge
Indicates that an entity is experiencing or associated with a difficulty, problem, or obstacle related to agriculture or farming activities.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c7ad888190b57bb987a8202789 |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:12 a.m.