Triple
T34871117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Empire in Kenya region |
E1005753
|
entity |
| Predicate | introducedCashCrop |
P17909
|
FINISHED |
| Object | coffee |
—
|
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: coffee | Statement: [British Empire in Kenya region, introducedCashCrop, coffee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedCashCrop Context triple: [British Empire in Kenya region, introducedCashCrop, coffee]
-
A.
introducedCrop
chosen
Indicates that an entity brought a crop species into a new area or context where it was not previously present or cultivated.
-
B.
firstCommercialCropType
Indicates the type of crop that was first grown commercially in a given context or location.
-
C.
majorCrop
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
D.
includedCropTraditionally
Indicates that one entity has historically or customarily contained or featured the other entity as a crop.
-
E.
historicalCultivation
Indicates that an entity has been traditionally grown, farmed, or otherwise cultivated in relation to another entity over a significant historical period.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4 p.m.