Triple
T11931982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disability Living Allowance |
E283935
|
entity |
| Predicate | ageGroupOriginallyCovered |
P19123
|
FINISHED |
| Object | people under 65 at date of claim |
—
|
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: people under 65 at date of claim | Statement: [Disability Living Allowance, ageGroupOriginallyCovered, people under 65 at date of claim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageGroupOriginallyCovered Context triple: [Disability Living Allowance, ageGroupOriginallyCovered, people under 65 at date of claim]
-
A.
ageGroup
chosen
Indicates the categorical age range or bracket to which an entity belongs.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageVariants
Indicates that one entity is an alternative form or version of another distinguished specifically by age (e.g., younger/older or different life-stage variants).
-
D.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
E.
ageGroupRole
Indicates the role or function an entity has within a specific age group classification.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90305015c81908edb0d9d3d012b2e |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.