Triple
T29836084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitta dosha |
E757660
|
entity |
| Predicate | balancedStateAssociatedWith |
P3520
|
FINISHED |
| Object | good digestion |
—
|
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: good digestion | Statement: [Pitta dosha, balancedStateAssociatedWith, good digestion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balancedStateAssociatedWith Context triple: [Pitta dosha, balancedStateAssociatedWith, good digestion]
-
A.
imbalancedStateAssociatedWith
Indicates an association between an entity and a condition in which some quantity, function, or state is out of balance or not in equilibrium.
-
B.
associatedState
chosen
Indicates that one entity is linked or connected to a particular state, condition, or status of another entity.
-
C.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
D.
positionAssociatedWith
Indicates a relationship where a specific role, job, or position is linked or connected to a particular entity, context, or resource.
-
E.
associatedStable
Indicates that one entity is linked or connected to a particular stable in a way that denotes an ongoing or defined association.
- 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_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. |
Created at: April 29, 2026, 5:37 p.m.