Triple
T25465447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanterman Developmental Disabilities Services Act |
E638158
|
entity |
| Predicate | serviceSettings |
P52736
|
FINISHED |
| Object | home-based services |
—
|
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: home-based services | Statement: [Lanterman Developmental Disabilities Services Act, serviceSettings, home-based services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceSettings Context triple: [Lanterman Developmental Disabilities Services Act, serviceSettings, home-based services]
-
A.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
B.
serviceSystem
chosen
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
-
C.
settingOfBusiness
Indicates the location or environment in which a business operates or conducts its activities.
-
D.
serviceUser
Indicates that one entity is a user or consumer of a service provided by another entity.
-
E.
campaignSetting
Indicates the broader narrative world or environment within which a particular campaign, story, or activity takes place.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 2:14 p.m.