Triple
T29584815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jimma |
E753691
|
entity |
| Predicate | coffeeHeritage |
P168157
|
FINISHED |
| Object | longstanding coffee cultivation history |
—
|
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: longstanding coffee cultivation history | Statement: [Jimma, coffeeHeritage, longstanding coffee cultivation history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coffeeHeritage Context triple: [Jimma, coffeeHeritage, longstanding coffee cultivation history]
-
A.
coffeeOrganization
Indicates a relationship where an organization is involved with coffee, such as producing, distributing, selling, or promoting it.
-
B.
coffeeProfile
Indicates the characteristic flavor, aroma, and strength attributes that define a particular coffee.
-
C.
coffeeIntroducedBy
Indicates that a particular coffee was brought, presented, or made known to someone by a specific person or source.
-
D.
coffeeDesignation
Indicates that one entity is designated or classified as a particular type, role, or category of coffee in relation to another entity.
-
E.
coffeeBrand
Indicates that one entity is a brand associated with the production or marketing of coffee products for the other entity.
- F. None of above. chosen
Provenance (4 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 6:09 p.m.