Triple
T20984550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Child Benefit Act 1975 |
E516860
|
entity |
| Predicate | introducedUnifiedBenefit |
P142366
|
FINISHED |
| Object | child benefit |
—
|
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: child benefit | Statement: [Child Benefit Act 1975, introducedUnifiedBenefit, child benefit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedUnifiedBenefit Context triple: [Child Benefit Act 1975, introducedUnifiedBenefit, child benefit]
-
A.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
B.
benefitProtection
Indicates that one entity provides protective advantages or safeguards that benefit another entity.
-
C.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
D.
benefitsLevel
Indicates the degree or extent to which one entity gains advantages, support, or positive outcomes from another entity or action.
-
E.
isIndividualBenefit
Indicates that something provides a benefit or advantage to a single individual rather than to a group or collective.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe1474c8190912b90da0973f99f |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:48 p.m.