Triple
T22458781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerala cuisine |
E555178
|
entity |
| Predicate | hasDish |
P17589
|
FINISHED |
| Object | appam |
—
|
NE NERFINISHED |
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: appam | Statement: [Kerala cuisine, hasDish, appam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: appam Context triple: [Kerala cuisine, hasDish, appam]
-
A.
Appam
chosen
Appam is a soft, bowl-shaped South Indian pancake made from fermented rice batter and coconut milk, commonly eaten for breakfast or dinner with curries in Kerala.
-
B.
appan
Appan is a South Indian male given name element commonly used in Tamil names, often conveying a sense of respect or endearment.
-
C.
Annappes
Annappes is a former commune in northern France that was incorporated into the new town of Villeneuve d’Ascq during municipal reorganizations in the 20th century.
-
D.
Apam Napat
Apam Napat is an ancient Vedic deity associated primarily with waters, often depicted as a fiery or luminous god emerging from or dwelling within them.
-
E.
Appar
Appar was a prominent 7th-century Tamil Shaivite saint and poet whose devotional hymns greatly shaped the Bhakti movement in South India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b7e01fc8190825c3dc024484440 |
completed | April 29, 2026, 1:14 a.m. |
Created at: April 16, 2026, 8:48 p.m.