Triple
T36443537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coffea |
E897801
|
entity |
| Predicate | arabicaOrigin |
P13358
|
FINISHED |
| Object | Ethiopian highlands |
—
|
NE NERFINISHED |
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: Ethiopian highlands | Statement: [Coffea, arabicaOrigin, Ethiopian highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arabicaOrigin Context triple: [Coffea, arabicaOrigin, Ethiopian highlands]
-
A.
coffeeIntroducedBy
Indicates that a particular coffee was brought, presented, or made known to someone by a specific person or source.
-
B.
coffeeSourcingRegion
chosen
Indicates the geographic region from which the coffee was originally sourced or obtained.
-
C.
arabicaPloidy
Indicates the ploidy level (number of chromosome sets) associated with Arabica in a given biological or genetic context.
-
D.
coffeeHeritage
Indicates a historical or cultural connection between entities and the tradition, origin, or legacy of coffee.
-
E.
coffeeVariety
Indicates a relationship where a specific type or variety of coffee is associated with a coffee-related entity (such as a product, beverage, or plant).
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.