Triple
T6649108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Existing Liabilities Scheme |
E150773
|
entity |
| Predicate | covers |
P1393
|
FINISHED |
| Object | claims arising from historic clinical negligence incidents |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: claims arising from historic clinical negligence incidents | Statement: [Existing Liabilities Scheme, covers, claims arising from historic clinical negligence incidents]
Provenance (2 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b01fea4c8190a21ba7f4c2018c5e |
completed | March 27, 2026, 4:28 p.m. |
Created at: March 27, 2026, 2:01 p.m.