Triple

T28696312
Position Surface form Disambiguated ID Type / Status
Subject Libyans E729424 entity
Predicate commonCuisineInfluence P39848 FINISHED
Object Mediterranean 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: Mediterranean cuisine | Statement: [Libyans, commonCuisineInfluence, Mediterranean cuisine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commonCuisineInfluence
Context triple: [Libyans, commonCuisineInfluence, Mediterranean cuisine]
  • A. cuisineInfluence chosen
    Indicates that one cuisine has had a notable impact on the development, style, or characteristics of another cuisine.
  • B. sharesCuisineWith
    Indicates that two entities offer or are associated with the same type or style of cuisine.
  • C. haveDistinctCulinaryTraditions
    Indicates that the related entities possess different and distinguishable culinary practices, cuisines, or food-related customs from one another.
  • D. regionOfCulinaryImportance
    Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
  • E. foodCulture
    Indicates the relationship between a place or group and its characteristic traditions, practices, and preferences surrounding food and eating.
  • 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_69f043e6e9688190b6bdd6e5665498ff completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69fbbc49da8c8190902bbb05d2477cab completed May 6, 2026, 10:10 p.m.
PD Predicate disambiguation batch_69fbb13f34b08190bbbb220ac1e6e666 completed May 6, 2026, 9:23 p.m.
Created at: April 28, 2026, 5:39 a.m.