Triple

T38275349
Position Surface form Disambiguated ID Type / Status
Subject Collecchio E1021933 entity
Predicate sharesCulinaryTraditionsWith P45241 FINISHED
Object Parma NE NERFINISHED

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: Parma | Statement: [Collecchio, sharesCulinaryTraditionsWith, Parma]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesCulinaryTraditionsWith
Context triple: [Collecchio, sharesCulinaryTraditionsWith, Parma]
  • A. haveDistinctCulinaryTraditions
    Indicates that the related entities possess different and distinguishable culinary practices, cuisines, or food-related customs from one another.
  • B. sharesCuisineWith chosen
    Indicates that two entities offer or are associated with the same type or style of cuisine.
  • C. 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.
  • D. sharesTraditionsWith
    Indicates that two entities have customs, practices, or cultural traditions in common or mutually observe similar traditional activities.
  • E. traditionalFoodBase
    Indicates that one entity serves as the primary ingredient, staple, or foundational component of a traditional food associated with another entity.
  • 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_69f76df0cddc81908d16c1556ff4097f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a00c8e617548190bba4cdfbb6f512e0 completed May 10, 2026, 6:05 p.m.
PD Predicate disambiguation batch_6a00c7e816b88190bd40f5ea2a768c8b completed May 10, 2026, 6:01 p.m.
Created at: May 3, 2026, 4:30 p.m.