Triple
T22716550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate Wales |
E561746
|
entity |
| Predicate | hasTherapeuticSpecialty |
P466
|
FINISHED |
| Object | anger management |
—
|
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: anger management | Statement: [Kate Wales, hasTherapeuticSpecialty, anger management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTherapeuticSpecialty Context triple: [Kate Wales, hasTherapeuticSpecialty, anger management]
-
A.
hasSpecialty
chosen
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
hasSpecialist
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
C.
supportsMedicalSpecialty
Indicates that one entity provides resources, infrastructure, or services that enable or facilitate the practice or development of a particular medical specialty.
-
D.
hasSpecialistStatus
Indicates that an entity holds a recognized specialist designation or status in a particular field, role, or context.
-
E.
offersSpecialtyCare
Indicates that an entity provides specialized or advanced care services beyond general or primary care.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790e14c88190af6acb27910ae9c1 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:19 p.m.