Triple
T6723124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHS Dental Exemption Certificates |
E153443
|
entity |
| Predicate | requiresRenewal |
P30609
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NHS Dental Exemption Certificates, requiresRenewal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresRenewal Context triple: [NHS Dental Exemption Certificates, requiresRenewal, true]
-
A.
renewalRequired
chosen
Indicates that an existing agreement, status, or authorization must be renewed to remain valid.
-
B.
laterRenewedFor
Indicates that an existing agreement, contract, or arrangement was renewed again at a subsequent, later time.
-
C.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
D.
isRenewable
Indicates that a resource or energy source can be naturally replenished or regenerated within a human-relevant timescale.
-
E.
renews
Indicates that one entity extends, refreshes, or restores the validity, duration, or effectiveness of another entity, often continuing a prior agreement, state, or condition.
- 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.