Triple
T20841718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHS Constitution for England |
E513117
|
entity |
| Predicate | includesValue |
P12721
|
FINISHED |
| Object | respect and dignity |
—
|
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: respect and dignity | Statement: [NHS Constitution for England, includesValue, respect and dignity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesValue Context triple: [NHS Constitution for England, includesValue, respect and dignity]
-
A.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
B.
valuesIn
Indicates that one entity specifies or constrains the set of permissible values for another entity.
-
C.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
D.
includesClause
chosen
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
E.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34be7a081909c9e98e7f7af7fde |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.