Triple

T21362599
Position Surface form Disambiguated ID Type / Status
Subject Lubliniec E526820 entity
Predicate hasRegionalCuisineInfluence P45120 FINISHED
Object Silesian 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: Silesian cuisine | Statement: [Lubliniec, hasRegionalCuisineInfluence, Silesian cuisine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegionalCuisineInfluence
Context triple: [Lubliniec, hasRegionalCuisineInfluence, Silesian cuisine]
  • A. cuisineInfluence
    Indicates that one cuisine has had a notable impact on the development, style, or characteristics of another cuisine.
  • B. includesRegionalCuisine
    Indicates that one entity incorporates or features the regional cuisine associated with another entity.
  • C. hasEthnicInfluence
    Indicates that one entity has a cultural, traditional, or ethnic impact on, or contributes to shaping the ethnic character of, another entity.
  • D. regionOfCulinaryImportance chosen
    Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
  • E. haveDistinctCulinaryTraditions
    Indicates that the related entities possess different and distinguishable culinary practices, cuisines, or food-related customs from one another.
  • 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_69e0b51d8a308190b09113b3b3f9bc15 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee5bad6a308190a9665734a0fb5f55 completed April 26, 2026, 6:38 p.m.
PD Predicate disambiguation batch_69e6162bbfc88190a3e75859941b2638 completed April 20, 2026, 12:03 p.m.
Created at: April 16, 2026, 5:08 p.m.