Triple
T18042157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Approved Contractor Scheme |
E431676
|
entity |
| Predicate | benefitForCustomer |
P101952
|
FINISHED |
| Object | assurance of minimum quality and performance standards |
—
|
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: assurance of minimum quality and performance standards | Statement: [Approved Contractor Scheme, benefitForCustomer, assurance of minimum quality and performance standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitForCustomer Context triple: [Approved Contractor Scheme, benefitForCustomer, assurance of minimum quality and performance standards]
-
A.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
B.
benefitAppliesTo
chosen
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
C.
benefitCharacteristic
Indicates that one entity possesses a quality or feature that provides an advantage, usefulness, or positive effect to another entity.
-
D.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
E.
benefitsMayInclude
Indicates that one entity lists or specifies possible advantages, gains, or positive outcomes that another entity may receive.
- 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_69e4bfef454c8190ad3787502f2bdd34 |
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.