Triple
T6875940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Prescription Service |
E158670
|
entity |
| Predicate | rollout |
P73878
|
FINISHED |
| Object | phased implementation across England |
—
|
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: phased implementation across England | Statement: [Electronic Prescription Service, rollout, phased implementation across England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rollout Context triple: [Electronic Prescription Service, rollout, phased implementation across England]
-
A.
relaunch
Indicates restarting or bringing back into operation something that was previously launched, often with changes or improvements.
-
B.
releaseType
Indicates the kind or category of a release event or version associated with an entity.
-
C.
launchOutcome
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
-
D.
releaseSequence
Indicates the ordered succession in which related items, such as versions or installments, are released over time.
-
E.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
- F. None of above. chosen
Provenance (4 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8cb76108190a5136240ed85d900 |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:22 p.m.