Triple
T1050403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Insurance contributions |
E22683
|
entity |
| Predicate | payableWhen |
P9379
|
FINISHED |
| Object | earnings exceed specified thresholds |
—
|
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: earnings exceed specified thresholds | Statement: [National Insurance contributions, payableWhen, earnings exceed specified thresholds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payableWhen Context triple: [National Insurance contributions, payableWhen, earnings exceed specified thresholds]
-
A.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
B.
isUnpaid
Indicates that an expected payment, fee, or financial obligation has not yet been made or settled.
-
C.
endedDueTo
Indicates that an event, process, or state came to a conclusion specifically because of a particular cause or condition.
-
D.
repaymentTrigger
chosen
Indicates that a specific event or condition causes a repayment obligation to become due or activated.
-
E.
acknowledgmentDate
Indicates the date on which an acknowledgment of something (such as receipt, notice, or information) is formally recorded or recognized.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b40d50819091cb37a2236e82ee |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b7309cc481908ed839b0b8d75dbf |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.