Triple
T19888873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freudian psychoanalysis |
E477975
|
entity |
| Predicate | viewsSymptomAs |
P112834
|
FINISHED |
| Object | compromise formation |
—
|
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: compromise formation | Statement: [Freudian psychoanalysis, viewsSymptomAs, compromise formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsSymptomAs Context triple: [Freudian psychoanalysis, viewsSymptomAs, compromise formation]
-
A.
viewsSymptoms
Indicates that one entity observes or examines the symptoms associated with another entity.
-
B.
viewOnIllness
chosen
Indicates the perspective, belief, or attitude that one entity holds about the nature, cause, or meaning of an illness affecting another entity.
-
C.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
D.
isUsedForSymptom
Indicates that something (such as a treatment, medication, or intervention) is employed to address, alleviate, or manage a particular symptom.
-
E.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590c1b9c8190abbfaa04b80713b3 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.