Triple
T9314958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSC in Northern Ireland |
E224093
|
entity |
| Predicate | costToPatients |
P5902
|
FINISHED |
| Object | mostly free at point of use |
—
|
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: mostly free at point of use | Statement: [HSC in Northern Ireland, costToPatients, mostly free at point of use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costToPatients Context triple: [HSC in Northern Ireland, costToPatients, mostly free at point of use]
-
A.
costToUser
chosen
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
B.
costModel
Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
-
C.
coversCosts
Indicates that one party assumes responsibility for paying or reimbursing the expenses incurred by another party.
-
D.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
E.
numberOfAnnualPatientVisits
Indicates the total count of patient visits that occur over the course of one year.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b2274481908ddb4eda70cea8cc |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.