Triple
T15806133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waja people |
E383220
|
entity |
| Predicate | livelihoodPractice |
P4104
|
FINISHED |
| Object | animal husbandry |
—
|
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: animal husbandry | Statement: [Waja people, livelihoodPractice, animal husbandry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livelihoodPractice Context triple: [Waja people, livelihoodPractice, animal husbandry]
-
A.
livelihood
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.
agriculturalPractice
chosen
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
-
E.
pastoralActivities
Indicates activities related to providing spiritual care, guidance, or religious leadership within a community.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52682548190998d8b6a08982877 |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.