Triple
T10866871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GOV.UK Notify |
E256551
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | GOV.UK Pay |
E256550
|
NE 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: GOV.UK Pay | Statement: [GOV.UK Notify, relatedTo, GOV.UK Pay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GOV.UK Pay Context triple: [GOV.UK Notify, relatedTo, GOV.UK Pay]
-
A.
GOV.UK Pay
chosen
GOV.UK Pay is a UK government digital payments platform that enables public sector services to take secure online card and alternative payments from users.
-
B.
WePay
WePay is an online payment services company that provides integrated payment processing solutions for platforms, marketplaces, and software providers.
-
C.
GOV.UK
GOV.UK is the United Kingdom government’s central online platform that provides official information, services, and guidance to the public and businesses.
-
D.
GOV.UK Verify
GOV.UK Verify is a UK government digital identity assurance service that allows citizens to securely prove who they are online when accessing public services.
-
E.
GOV.UK Notify
GOV.UK Notify is a UK government digital platform that lets public sector services send emails, text messages, and letters to users quickly and at scale.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516e15448190aefdba1aa635baea |
completed | April 9, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7d7b32081909dd5f8ae3fe293be |
completed | April 15, 2026, 8:40 p.m. |
Created at: April 8, 2026, 9:20 p.m.