Triple

T4411866
Position Surface form Disambiguated ID Type / Status
Subject Japanese Brazilians E94868 entity
Predicate introducedCuisine P39848 FINISHED
Object sushi 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: sushi | Statement: [Japanese Brazilians, introducedCuisine, sushi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedCuisine
Context triple: [Japanese Brazilians, introducedCuisine, sushi]
  • A. cuisineType
    Indicates the type or style of food associated with an entity, such as a restaurant or dish.
  • B. regionOfCulinaryImportance
    Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
  • C. cuisine
    Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
  • D. cuisineInfluence chosen
    Indicates that one cuisine has had a notable impact on the development, style, or characteristics of another cuisine.
  • E. cuisineFeature
    Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
  • 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_69b34539638c8190abfea3eb29425210 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b354e656dc819093ca8395d7334006 completed March 13, 2026, 12:05 a.m.
PD Predicate disambiguation batch_69b34f5d0c54819085c08533bb58030a completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:29 p.m.