Triple
T35847598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coscomatepec |
E1036256
|
entity |
| Predicate | hasCoffeeGrowingTradition |
P168157
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Coscomatepec, hasCoffeeGrowingTradition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoffeeGrowingTradition Context triple: [Coscomatepec, hasCoffeeGrowingTradition, true]
-
A.
hasCoffeeCulture
Indicates that a place or group is characterized by established social practices, traditions, and norms centered around the consumption and appreciation of coffee.
-
B.
coffeeHeritage
chosen
Indicates a historical or cultural connection between entities and the tradition, origin, or legacy of coffee.
-
C.
partOfCoffeeRegion
Indicates that one entity is a subregion or component area within a larger coffee-producing region.
-
D.
coffeeGrownOnSlopes
Indicates that coffee is cultivated on the sloping terrain of a particular geographic area.
-
E.
coffeeIntroducedBy
Indicates that a particular coffee was brought, presented, or made known to someone by a specific person or source.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.