Triple

T13300410
Position Surface form Disambiguated ID Type / Status
Subject Jalapa E316794 entity
Predicate nearbyAgriculturalProduct P75269 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: [Jalapa, nearbyAgriculturalProduct, coffee]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearbyAgriculturalProduct
Context triple: [Jalapa, nearbyAgriculturalProduct, coffee]
  • A. agriculturalProduce chosen
    Indicates that one entity is an agricultural product (such as crops or livestock-derived goods) produced by or associated with another entity.
  • B. traditionalAgriculturalProduct
    Indicates that something is recognized as an agricultural product produced using long-established, customary methods and practices.
  • C. hasNearbyAgriculturalActivity
    Indicates that an entity is located close enough to agricultural operations or land use for those activities to be considered relevant or influential to it.
  • D. usesLocalProduce
    Indicates that one entity obtains and incorporates agricultural products sourced from nearby or locally based producers.
  • E. commodityProduced
    Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
  • 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99cfdc9388190af1fdd3cd4717bd8 completed April 11, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69d98f6893708190aeebf4c47386cff7 completed April 11, 2026, 12:01 a.m.
Created at: April 9, 2026, 9:28 p.m.