Triple

T18382980
Position Surface form Disambiguated ID Type / Status
Subject Taisho-ku E446502 entity
Predicate hasLocalCuisineInfluence P39848 FINISHED
Object Okinawan 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: Okinawan cuisine | Statement: [Taisho-ku, hasLocalCuisineInfluence, Okinawan cuisine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalCuisineInfluence
Context triple: [Taisho-ku, hasLocalCuisineInfluence, Okinawan cuisine]
  • A. cuisineInfluence chosen
    Indicates that one cuisine has had a notable impact on the development, style, or characteristics of another cuisine.
  • B. haveCuisine
    Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular 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. hasLocalCult
    Indicates that an entity is associated with a cult or worship practice that is specific to a particular locality or region.
  • E. hasEthnicInfluence
    Indicates that one entity has a cultural, traditional, or ethnic impact on, or contributes to shaping the ethnic character of, 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_69d8b9f370b88190b1e5081c2c238e7f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e5179c931c8190b1c7c8284f42f7b7 completed April 19, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69e44ff1f92c8190afbb8e85d12bf2a9 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:45 a.m.