Triple
T18041449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DBS certificate |
E431661
|
entity |
| Predicate | feeExemption |
P36416
|
FINISHED |
| Object | some volunteer roles |
—
|
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: some volunteer roles | Statement: [DBS certificate, feeExemption, some volunteer roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeExemption Context triple: [DBS certificate, feeExemption, some volunteer roles]
-
A.
exemptedFrom
chosen
Indicates that an entity is not subject to, or is formally released from, a rule, obligation, requirement, or liability that would otherwise apply.
-
B.
providesExemptionsTo
Indicates that one entity grants or offers exemptions, waivers, or exceptions from rules, obligations, or requirements to another entity.
-
C.
exemptionType
Indicates the specific category or kind of exemption that applies in a given context.
-
D.
tollExemption
Indicates that an entity is not required to pay a toll or fee that would normally be charged for using a particular route, facility, or service.
-
E.
feeAccess
Indicates that access to something is granted only upon payment of a fee or charge.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bfee78048190b3fada0eb3d28c77 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.