Triple
T23350214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Individualized Family Service Plan |
E591984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | family-centered service plan |
C47548
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: family-centered service plan Context triple: [Individualized Family Service Plan, instanceOf, family-centered service plan]
-
A.
family partnership
A family partnership is a business arrangement in which two or more family members jointly own and operate an enterprise, sharing profits, losses, management responsibilities, and legal obligations according to an agreed partnership structure.
-
B.
family management system
A family management system is a centralized platform that helps households coordinate schedules, tasks, finances, and communication to streamline daily family life and responsibilities.
-
C.
family role
A family role is a socially and emotionally defined position an individual holds within a family system, encompassing expected behaviors, responsibilities, and relationships with other family members.
-
D.
family therapist
A family therapist is a mental health professional who helps families and couples understand and improve their relationships by addressing communication patterns, conflicts, and emotional dynamics within the family system.
-
E.
family pooling program
A family pooling program is a system that allows multiple family members to combine and share resources, benefits, or usage limits (such as points, data, or credits) under a single collective account.
- F. None of above. chosen
Provenance (1 batch)
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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:19 p.m.