Triple
T25098146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarrazú |
E628646
|
entity |
| Predicate | coffeeCertification |
P72097
|
FINISHED |
| Object | specialty-grade lots |
—
|
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: specialty-grade lots | Statement: [Tarrazú, coffeeCertification, specialty-grade lots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coffeeCertification Context triple: [Tarrazú, coffeeCertification, specialty-grade lots]
-
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.
coffeeDesignation
Indicates that one entity is designated or classified as a particular type, role, or category of coffee in relation to another entity.
-
D.
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).
-
E.
coffeeDesignationType
chosen
Indicates the specific classification or type designation assigned to a coffee (e.g., by quality, origin, or regulatory category).
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464ba4e148190a8169ac91b2f85b6 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:25 a.m.