Triple
T21013328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMS |
E517606
|
entity |
| Predicate | responseSetting |
P142481
|
FINISHED |
| Object | Out-of-hospital settings |
—
|
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: Out-of-hospital settings | Statement: [EMS, responseSetting, Out-of-hospital settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseSetting Context triple: [EMS, responseSetting, Out-of-hospital settings]
-
A.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
B.
responseField
Indicates that a particular piece of information is included as part of a response or output structure.
-
C.
responseExample
Indicates that one entity serves as an illustrative or sample response corresponding to another entity (such as a prompt, question, or situation).
-
D.
responseExpected
Indicates that a reply, action, or follow-up is anticipated from a specified party in relation to a prior communication or event.
-
E.
responseFormula
Indicates that one entity’s reaction, reply, or outcome is expressed or encoded in a specific formula or structured representation.
- F. None of above. chosen
Provenance (4 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc41d57881908b9ab17d1844a8d0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:54 p.m.