Triple
T24509863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Hospital Detox Program |
E606185
|
entity |
| Predicate | usedTreatmentMethod |
P78752
|
FINISHED |
| Object | acupuncture |
—
|
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: acupuncture | Statement: [Lincoln Hospital Detox Program, usedTreatmentMethod, acupuncture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTreatmentMethod Context triple: [Lincoln Hospital Detox Program, usedTreatmentMethod, acupuncture]
-
A.
usesTreatment
chosen
Indicates that one entity applies or employs a particular treatment or therapeutic method on or for another entity.
-
B.
hasReceivedTreatmentFor
Indicates that an entity has undergone or been given a treatment in relation to a specified condition, issue, or problem.
-
C.
treatmentType
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
-
D.
treatment
Indicates that one entity is used as a medical or therapeutic intervention to address, manage, or cure a condition affecting another entity.
-
E.
hasCommonTreatment
Indicates that two or more entities share at least one treatment method or therapeutic approach in common.
- 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:23 a.m.