Triple
T17382045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Government Finance Act 1988 |
E422591
|
entity |
| Predicate | reformedTax |
P125139
|
FINISHED |
| Object | non-domestic rates |
—
|
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: non-domestic rates | Statement: [Local Government Finance Act 1988, reformedTax, non-domestic rates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformedTax Context triple: [Local Government Finance Act 1988, reformedTax, non-domestic rates]
-
A.
reformedOn
Indicates that an entity underwent a reform, change, or restructuring at a specific point in time or on a particular date.
-
B.
typeOfTaxChange
chosen
Indicates a relationship where one entity represents a specific kind or category of tax modification described or classified by another entity.
-
C.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
D.
replacedInReform
Indicates that one entity was substituted or superseded by another as part of a formal reform or restructuring process.
-
E.
reformerOf
Indicates that one entity is the person or agent who initiated or carried out significant reforms or changes to another entity.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a86d8cc81909281b22f5da87d70 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.