Triple

T23383837
Position Surface form Disambiguated ID Type / Status
Subject Beyond Sausage E593822 entity
Predicate flavorDesignedToMimic P135360 FINISHED
Object traditional pork sausage taste 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: traditional pork sausage taste | Statement: [Beyond Sausage, flavorDesignedToMimic, traditional pork sausage taste]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: flavorDesignedToMimic
Context triple: [Beyond Sausage, flavorDesignedToMimic, traditional pork sausage taste]
  • A. isFlavored
    Indicates that one entity imparts a particular taste or flavor characteristic to another entity.
  • B. isOfficialFlavorOf
    Indicates that one item is formally recognized or designated as an official flavor associated with another entity (such as a brand, product line, or event).
  • C. typicalFlavor
    Indicates that something characteristically has or is associated with a particular flavor.
  • D. flavorDevelopment
    Indicates the process by which the taste characteristics of something change or intensify over time or through specific conditions or treatments.
  • E. intendedFlavorProfile chosen
    Indicates the flavor characteristics that something is designed or planned to have, rather than what it actually tastes like.
  • 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_69e25d2754fc819085deea939bde60ab completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a496ae34819090e86c89eef6d2dc completed April 29, 2026, 6:26 a.m.
PD Predicate disambiguation batch_69f061dde2e481908308952f9c0d3c2e completed April 28, 2026, 7:29 a.m.
Created at: April 17, 2026, 5:34 p.m.