Triple
T7487356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aguadas |
E176914
|
entity |
| Predicate | coffeeRegionStatus |
P23251
|
FINISHED |
| Object | part of Colombian coffee-growing region |
—
|
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: part of Colombian coffee-growing region | Statement: [Aguadas, coffeeRegionStatus, part of Colombian coffee-growing region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coffeeRegionStatus Context triple: [Aguadas, coffeeRegionStatus, part of Colombian coffee-growing region]
-
A.
wineRegionStatus
Indicates the official classification or recognition status assigned to a wine-producing region.
-
B.
coffeeSourcingRegion
Indicates the geographic region from which the coffee was originally sourced or obtained.
-
C.
regionStatus
chosen
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
-
D.
statusInRegion
Indicates the specific status or condition an entity holds within a particular geographic or administrative region.
-
E.
teaProductionRegion
Indicates the region or area where tea is produced or cultivated.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5582adc81908b68439762965d88 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.