Triple
T25233039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapha |
E632264
|
entity |
| Predicate | aggravatedBy |
P141891
|
FINISHED |
| Object | oily foods |
—
|
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: oily foods | Statement: [Kapha, aggravatedBy, oily foods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggravatedBy Context triple: [Kapha, aggravatedBy, oily foods]
-
A.
correctsAberration
Indicates that one entity counteracts, fixes, or compensates for an error, flaw, or deviation present in another entity.
-
B.
significantlyIntensifiedAfter
Indicates that one condition, effect, or quality became much stronger or more pronounced following another event or state.
-
C.
intensifiedOver
chosen
Indicates that one entity increases the degree, strength, or intensity of another entity or condition beyond its previous level.
-
D.
wrongedBy
Indicates that one entity has been harmed, treated unjustly, or suffered a grievance as a result of another entity's actions.
-
E.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47df5eafc819089a2735bd8177a27 |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:06 p.m.