Triple
T17391896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirkbride Plan |
E422842
|
entity |
| Predicate | hasTreatmentAspect |
P127307
|
FINISHED |
| Object | structured daily activities |
—
|
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: structured daily activities | Statement: [Kirkbride Plan, hasTreatmentAspect, structured daily activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreatmentAspect Context triple: [Kirkbride Plan, hasTreatmentAspect, structured daily activities]
-
A.
hasTreatmentConsideration
Indicates that a particular factor, condition, or option should be taken into account when planning, selecting, or managing a treatment.
-
B.
hasSubjectTreatment
Indicates that a subject is receiving, has received, or is associated with a particular treatment or therapeutic intervention.
-
C.
hasReceivedTreatmentFor
Indicates that an entity has undergone or been given a treatment in relation to a specified condition, issue, or problem.
-
D.
hasCommonTreatment
Indicates that two or more entities share at least one treatment method or therapeutic approach in common.
-
E.
hasSubsequentTreatment
Indicates that one treatment occurs after and in continuation of another treatment in a temporal sequence.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43aba5398819096846bdeefde0788 |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.