Triple
T9277225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Western Ambulance Service |
E222978
|
entity |
| Predicate | servicePriority |
P25884
|
FINISHED |
| Object | emergency care |
—
|
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: emergency care | Statement: [South Western Ambulance Service, servicePriority, emergency care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servicePriority Context triple: [South Western Ambulance Service, servicePriority, emergency care]
-
A.
managementPriority
Indicates the relative level of importance or urgency assigned to managing or addressing a particular entity, issue, or task.
-
B.
supportsPriority
Indicates that one entity provides functionality or capability for handling or honoring priority levels associated with another entity or operation.
-
C.
upgradePriority
Indicates the relative importance or urgency assigned to performing an upgrade compared to other potential upgrades or tasks.
-
D.
planningPriority
Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
-
E.
typeOfPriority
chosen
Indicates the specific priority level or category assigned to something relative to other items or tasks.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07c95a98819098528b7ada37ddc1 |
completed | April 1, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.