Triple
T34983500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutory Sick Pay |
E1008879
|
entity |
| Predicate | payableBy |
P12961
|
FINISHED |
| Object | employer |
—
|
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: employer | Statement: [Statutory Sick Pay, payableBy, employer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payableBy Context triple: [Statutory Sick Pay, payableBy, employer]
-
A.
payableFor
Indicates that one entity is required to make or is subject to a payment in exchange for another entity, such as a good, service, or obligation.
-
B.
payableFrom
Indicates that a payment or monetary obligation is sourced, funded, or discharged from a specified account, entity, or resource.
-
C.
payableAs
Indicates that one entity is obligated or designated to be paid in the form, manner, or capacity specified by another entity.
-
D.
payableIn
Indicates that a specified amount, obligation, or transaction must be settled using a particular currency, asset, or payment medium.
-
E.
paidBy
chosen
Indicates that a payment or financial obligation is made or settled by the specified 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.