Triple

T36696227
Position Surface form Disambiguated ID Type / Status
Subject Northern Kerala E906097 entity
Predicate knownFor P22 FINISHED
Object Malabar cuisine
Malabar cuisine is a distinctive culinary tradition from northern Kerala in India, noted for its rich use of spices, coconut, seafood, and influences from Arab and Mughal cooking.
E555178 NE 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: Malabar cuisine | Statement: [Northern Kerala, knownFor, Malabar cuisine]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Malabar cuisine
Triple: [Northern Kerala, knownFor, Malabar cuisine]
Generated description
Malabar cuisine is a distinctive culinary tradition from northern Kerala in India, noted for its rich use of spices, coconut, seafood, and influences from Arab and Mughal cooking.

Provenance (5 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_69f76e70d2448190bdd3ce781ba971c5 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c7ea60c481908ea2ee276acea5dc completed May 3, 2026, 10:10 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a3824428881909e79dfa8f1858bda completed June 23, 2026, 7:39 a.m.
NEDg Description generation batch_6a3a38a32c9481909b133bfd99520e50 completed June 23, 2026, 7:41 a.m.
NED2 Entity disambiguation (via description) batch_6a3a3a91ef8c819086b3b5633154063a completed June 23, 2026, 7:49 a.m.
Created at: May 3, 2026, 4:12 p.m.