Triple
T19474504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baiga |
E487208
|
entity |
| Predicate | livelihoodSource |
P29524
|
FINISHED |
| Object | minor forest produce |
—
|
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: minor forest produce | Statement: [Baiga, livelihoodSource, minor forest produce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livelihoodSource Context triple: [Baiga, livelihoodSource, minor forest produce]
-
A.
livelihood
chosen
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
B.
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.
-
C.
livelihoodVulnerability
Indicates the degree to which an entity’s means of making a living are exposed or susceptible to harm, disruption, or loss.
-
D.
sourceForLife
Indicates that one entity serves as the origin, provider, or sustaining basis of life for another entity.
-
E.
socioEconomicBase
Indicates a foundational socio-economic relationship where one entity serves as the economic or social basis, support, or underlying structure for another.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633ef69508190b0d71ef663ba8977 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.