Triple
T36046025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malvani cuisine |
E1042671
|
entity |
| Predicate | Malvani masala |
P102161
|
FINISHED |
| Object | is a special spice blend used in Malvani 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: is a special spice blend used in Malvani cuisine | Statement: [Malvani cuisine, Malvani masala, is a special spice blend used in Malvani cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Malvani masala Context triple: [Malvani cuisine, Malvani masala, is a special spice blend used in Malvani cuisine]
-
A.
curdType
Indicates the specific kind or category of curd associated with an entity.
-
B.
typicalSpices
chosen
Indicates that certain spices are commonly or characteristically used in association with a particular dish, cuisine, or ingredient.
-
C.
commonSpicesInPithla
Indicates that the specified items are spices typically used in preparing the dish pithla.
-
D.
سلطة
Indicates a relationship where one entity holds power, control, or authoritative influence over another entity or situation.
-
E.
isTypicallyGarnishedWith
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.