Triple
T25306499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Area Agencies on Aging in California |
E634493
|
entity |
| Predicate | targetPopulationAge |
P17586
|
FINISHED |
| Object | 60 and older |
—
|
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: 60 and older | Statement: [Area Agencies on Aging in California, targetPopulationAge, 60 and older]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPopulationAge Context triple: [Area Agencies on Aging in California, targetPopulationAge, 60 and older]
-
A.
targetedPopulation
chosen
Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
-
B.
populationAge
Indicates the age or age distribution of a population associated with an entity.
-
C.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
D.
ageGroupInvolved
Indicates that a particular age group participates in, is affected by, or is otherwise involved in the specified event or relationship.
-
E.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 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, 1:25 p.m.