Triple
T34983640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WRAG |
E1008882
|
entity |
| Predicate | associatedWithBenefit |
P101952
|
FINISHED |
| Object | Employment and Support Allowance |
E59459
|
NE 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: Employment and Support Allowance | Statement: [WRAG, associatedWithBenefit, Employment and Support Allowance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBenefit Context triple: [WRAG, associatedWithBenefit, Employment and Support Allowance]
-
A.
benefitAdministered
Indicates that a benefit (such as aid, service, or entitlement) has been formally provided or delivered to an eligible recipient by an administering party.
-
B.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
C.
affectsBenefit
Indicates that one entity has an influence on, modifies, or determines the benefit or advantage received by another entity.
-
D.
benefitAppliesTo
chosen
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
E.
allianceBenefit
Indicates that one party gains an advantage, support, or positive outcome as a result of being in an alliance with another party.
- F. None of above.
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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cfd7d09c8190812814beaa8c7024 |
completed | June 21, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.