Triple
T12903352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welfare Reform Act 2007 |
E308665
|
entity |
| Predicate | reformsBenefit |
P107365
|
FINISHED |
| Object | Incapacity 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: Incapacity Benefit | Statement: [Welfare Reform Act 2007, reformsBenefit, Incapacity Benefit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformsBenefit Context triple: [Welfare Reform Act 2007, reformsBenefit, Incapacity Benefit]
-
A.
reformsBy
Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another entity.
-
B.
relatedReforms
Indicates that one reform is connected or associated with another reform, typically through shared goals, content, or impact.
-
C.
associatedReforms
Indicates a relationship where certain reforms are linked or connected to a given entity, such as a policy, event, or individual.
-
D.
typeOfReforms
Indicates the specific kinds or categories of reforms associated with an entity or situation.
-
E.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971820e008190bf8bc7c392c8bcbb |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:40 p.m.