Triple
T29836101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitta dosha |
E757660
|
entity |
| Predicate | aggravatedByTaste |
P167649
|
FINISHED |
| Object | sour taste |
—
|
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: sour taste | Statement: [Pitta dosha, aggravatedByTaste, sour taste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggravatedByTaste Context triple: [Pitta dosha, aggravatedByTaste, sour taste]
-
A.
hasTasteIntensity
Indicates the degree or strength of taste associated with something.
-
B.
palatability
Indicates how pleasing or acceptable something is to the senses, especially taste, often influencing preference or consumption.
-
C.
tasteInfluence
Indicates how one entity’s characteristics, actions, or presence affect or shape another entity’s preferences, likes, or aesthetic tastes.
-
D.
mouthfeel
Indicates the sensory qualities and physical sensations a substance produces in the mouth when consumed.
-
E.
tasteComparedTo
Indicates a comparison of the taste or flavor of one entity relative to another.
- F. None of above. chosen
Provenance (4 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67605e9548190855ca2d77608b4dc |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66bd123108190b451eb6e23842adb |
completed | May 2, 2026, 9:25 p.m. |
Created at: April 29, 2026, 5:37 p.m.