Triple

T24732054
Position Surface form Disambiguated ID Type / Status
Subject Acre E618311 entity
Predicate regionalCuisineFeature P17157 FINISHED
Object dishes based on fish and manioc 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: dishes based on fish and manioc | Statement: [Acre, regionalCuisineFeature, dishes based on fish and manioc]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionalCuisineFeature
Context triple: [Acre, regionalCuisineFeature, dishes based on fish and manioc]
  • A. includesRegionalCuisine
    Indicates that one entity incorporates or features the regional cuisine associated with another entity.
  • B. cuisineFeature chosen
    Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
  • C. regionOfCulinaryImportance
    Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
  • D. foodCulture
    Indicates the relationship between a place or group and its characteristic traditions, practices, and preferences surrounding food and eating.
  • E. regionalCharacteristic
    Indicates that a particular feature, quality, or attribute is typical of, or distinctive to, a specific geographic region.
  • 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_69e2fab772608190b74163751047ff50 completed April 18, 2026, 3:29 a.m.
NER Named-entity recognition batch_69f497bc12b881908fe3386c66252bf6 completed May 1, 2026, 12:08 p.m.
PD Predicate disambiguation batch_69f49366e8d08190adb4b71fe3a14683 completed May 1, 2026, 11:49 a.m.
Created at: April 18, 2026, 4:02 a.m.