Triple
T16399649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAYE tax system |
E398276
|
entity |
| Predicate | deductionsInclude |
P1393
|
FINISHED |
| Object | employee National Insurance contributions |
—
|
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: employee National Insurance contributions | Statement: [PAYE tax system, deductionsInclude, employee National Insurance contributions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deductionsInclude Context triple: [PAYE tax system, deductionsInclude, employee National Insurance contributions]
-
A.
taxDeductible
Indicates that an expense, contribution, or item is eligible to be subtracted from taxable income under applicable tax rules.
-
B.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
obligationsInclude
Indicates that one obligation set or entity’s responsibilities contain or encompass another specified obligation or subset of duties.
-
D.
usedInTaxPayments
Indicates that something is employed or applied as part of making or fulfilling tax payments.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cea4e481908400b852a5a7032a |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.