Triple
T28325237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Lowen |
E717386
|
entity |
| Predicate | therapyApproach |
P73063
|
FINISHED |
| Object | bioenergetic analysis |
—
|
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: bioenergetic analysis | Statement: [Alexander Lowen, therapyApproach, bioenergetic analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: therapyApproach Context triple: [Alexander Lowen, therapyApproach, bioenergetic analysis]
-
A.
therapeuticOrientation
chosen
Indicates the specific therapeutic approach or framework a practitioner uses when providing psychological or counseling treatment.
-
B.
treatment
Indicates that one entity is used as a medical or therapeutic intervention to address, manage, or cure a condition affecting another entity.
-
C.
proposedTreatment
Indicates that one entity is suggested or recommended as a possible treatment or therapeutic intervention for another entity.
-
D.
treatmentType
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
-
E.
careApproach
Indicates the method, strategy, or manner in which care or support is provided to someone or something.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6492da6f081908a86dba0ffef5610 |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:27 a.m.