Triple
T1313923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Care Quality Commission |
E28056
|
entity |
| Predicate | issuesRatingScale |
P16725
|
FINISHED |
| Object | outstanding |
—
|
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: outstanding | Statement: [Care Quality Commission, issuesRatingScale, outstanding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuesRatingScale Context triple: [Care Quality Commission, issuesRatingScale, outstanding]
-
A.
rating
Indicates an evaluation relationship where one entity assigns a qualitative or quantitative score or judgment to another entity.
-
B.
ratingSystem
Indicates a system or method used to assign evaluative scores or rankings to items, actions, or entities based on defined criteria.
-
C.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
D.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
E.
scoreScale
chosen
Indicates the scale or range on which a score or rating is expressed or measured.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1585d3081909ca0221c23de63ba |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.