Triple
T20406047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hospital Readmissions Reduction Program |
E500470
|
entity |
| Predicate | targetsCondition |
P31662
|
FINISHED |
| Object | acute myocardial infarction |
—
|
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: acute myocardial infarction | Statement: [Hospital Readmissions Reduction Program, targetsCondition, acute myocardial infarction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsCondition Context triple: [Hospital Readmissions Reduction Program, targetsCondition, acute myocardial infarction]
-
A.
targetedCondition
chosen
Indicates that an action, intervention, or entity is specifically directed toward affecting, treating, or addressing a particular condition.
-
B.
featuresCondition
Indicates that an entity includes, exhibits, or is characterized by a particular condition.
-
C.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
-
D.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
E.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67992cfb88190ae49a1723e6667a1 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.