Triple

T62185
Position Surface form Disambiguated ID Type / Status
Subject nopal cactus E1235 entity
Predicate associatedWithCuisine P2830 FINISHED
Object Mexican cuisine 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: Mexican cuisine | Statement: [nopal cactus, associatedWithCuisine, Mexican cuisine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithCuisine
Context triple: [nopal cactus, associatedWithCuisine, Mexican cuisine]
  • A. traditionalCuisine
    Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
  • B. isAssociatedWith chosen
    Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
  • C. notablyAssociatedWith
    Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
  • D. hasAssociatedCulture
    Indicates that an entity is related to, influenced by, or characterized by a particular culture.
  • E. hasCulturalSignificanceFor
    Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
  • 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_69a24ba4f760819081f6638a3c70538a completed Feb. 28, 2026, 1:57 a.m.
NER Named-entity recognition batch_69a251f74b0881909ad89127b8171277 completed Feb. 28, 2026, 2:24 a.m.
PD Predicate disambiguation batch_69a24ea242c8819086fe00bf01e6523e completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:02 a.m.