Triple
T25233030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapha |
E632264
|
entity |
| Predicate | balancedStateCharacterizedBy |
P662
|
FINISHED |
| Object | emotional stability |
—
|
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: emotional stability | Statement: [Kapha, balancedStateCharacterizedBy, emotional stability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balancedStateCharacterizedBy Context triple: [Kapha, balancedStateCharacterizedBy, emotional stability]
-
A.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
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.
-
C.
ruleCharacterization
Indicates that one rule is described, defined, or characterized in terms of another rule or set of rules.
-
D.
resultCharacterization
Indicates how the outcome of an event, process, or action is qualitatively described or characterized.
-
E.
relationshipCharacterizedAs
Indicates that one relationship is described, defined, or typified in terms of another specified characteristic or relational type.
- 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.