Triple

T35256552
Position Surface form Disambiguated ID Type / Status
Subject Kalasin E1018245 entity
Predicate hasCuisine P1016 FINISHED
Object Isan cuisine
Isan cuisine is the distinctive, often spicy and herb-forward food tradition of northeastern Thailand, known for dishes like som tam (papaya salad), larb (minced meat salad), and sticky rice.
E2135324 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: Isan cuisine | Statement: [Kalasin, hasCuisine, Isan 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: Isan cuisine
Triple: [Kalasin, hasCuisine, Isan cuisine]
Generated description
Isan cuisine is the distinctive, often spicy and herb-forward food tradition of northeastern Thailand, known for dishes like som tam (papaya salad), larb (minced meat salad), and sticky rice.

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_69f76de407d081909dfc3c419817ae93 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78f66bfd8819095abc3999599e0ec completed May 3, 2026, 6:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3819d554a88190aacfa5675c045370 completed June 21, 2026, 5:05 p.m.
NEDg Description generation batch_6a381ad38af88190a5a799b1651b8840 completed June 21, 2026, 5:09 p.m.
NED2 Entity disambiguation (via description) batch_6a381b78cc2c8190adcfc95407d338e8 completed June 21, 2026, 5:12 p.m.
Created at: May 3, 2026, 4:02 p.m.