Triple
T12588144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birhor |
E300520
|
entity |
| Predicate | shiftInLivelihood |
P84164
|
FINISHED |
| Object | wage labor |
—
|
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: wage labor | Statement: [Birhor, shiftInLivelihood, wage labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shiftInLivelihood Context triple: [Birhor, shiftInLivelihood, wage labor]
-
A.
livelihoodChange
chosen
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.
-
B.
livelihood
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
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.
agriculturalShiftTo
Indicates a change or transition in agricultural practices, production, or land use from one type, method, or crop to another.
-
E.
agriculturalImpact
Indicates the effect that an action, condition, or entity has on agricultural systems, productivity, or practices.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:06 p.m.