Triple
T6799795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gestalt therapy |
E156153
|
entity |
| Predicate | viewsSymptoms |
P73065
|
FINISHED |
| Object | as interruptions in self-regulation |
—
|
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: as interruptions in self-regulation | Statement: [Gestalt therapy, viewsSymptoms, as interruptions in self-regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsSymptoms Context triple: [Gestalt therapy, viewsSymptoms, as interruptions in self-regulation]
-
A.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
B.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
C.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
D.
causeOfIllness
Indicates that one entity is the reason or source responsible for another entity’s illness or disease.
-
E.
symptomAssociatedWithInfection
Indicates that a particular symptom is linked to, or commonly occurs as a result of, a specific infection.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e457408190a0ad9b0c48d8147c |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d2a8f9188190abbb8c730e7b5edf |
completed | March 27, 2026, 6:55 p.m. |
Created at: March 27, 2026, 2:15 p.m.