Triple
T6364481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper East Region |
E143190
|
entity |
| Predicate | majorLivelihoodActivity |
P29524
|
FINISHED |
| Object | subsistence farming |
—
|
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: subsistence farming | Statement: [Upper East Region, majorLivelihoodActivity, subsistence farming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorLivelihoodActivity Context triple: [Upper East Region, majorLivelihoodActivity, subsistence farming]
-
A.
majorActivity
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
B.
formerEconomicActivity
Indicates that an entity previously engaged in a specified economic activity but no longer does so.
-
C.
livelihood
chosen
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
D.
hasEconomicActivity
Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
-
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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680ed0148190b6e310b15b3449ff |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.