Triple
T2883868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Employment and Support Allowance |
E59459
|
entity |
| Predicate | payableTo |
P41188
|
FINISHED |
| Object | employees |
—
|
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: employees | Statement: [Employment and Support Allowance, payableTo, employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payableTo Context triple: [Employment and Support Allowance, payableTo, employees]
-
A.
canBePaidTo
chosen
Indicates that one entity is allowed or able to transfer payment to another entity.
-
B.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
C.
givenTo
Indicates that something is transferred or presented by one entity to another as a recipient.
-
D.
individualRecipient
Indicates that a specific individual is the direct recipient or beneficiary of something (such as an item, message, or action).
-
E.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02e0ec48190b969ed921d179560 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.