Triple
T11864436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welfare Reform Act 2012 |
E282245
|
entity |
| Predicate | underOccupancyPenaltyNickname |
P11214
|
FINISHED |
| Object | bedroom tax |
—
|
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: bedroom tax | Statement: [Welfare Reform Act 2012, underOccupancyPenaltyNickname, bedroom tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underOccupancyPenaltyNickname Context triple: [Welfare Reform Act 2012, underOccupancyPenaltyNickname, bedroom tax]
-
A.
nameUsedToAccommodate
Indicates that a particular name was previously used to refer to or accommodate an entity, but is no longer its current or primary name.
-
B.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
C.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
D.
allowedOccupationOf
Indicates that one entity is permitted or authorized to hold or perform the occupation associated with another entity.
-
E.
localNickname
chosen
Indicates that an entity is known by a particular nickname within a specific local or regional context.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73883508190a78b5f4ba4a220df |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.