Triple
T23650453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entresto |
E584152
|
entity |
| Predicate | containsSubstanceRole |
P153039
|
FINISHED |
| Object | neprilysin inhibitor |
—
|
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: neprilysin inhibitor | Statement: [Entresto, containsSubstanceRole, neprilysin inhibitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSubstanceRole Context triple: [Entresto, containsSubstanceRole, neprilysin inhibitor]
-
A.
hasSubstance
Indicates that one entity contains, consists of, or is composed of a particular substance or material.
-
B.
requiresSubstance
Indicates that one entity depends on or needs a particular substance in order to function, occur, or be valid.
-
C.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
D.
isSubstrateOf
Indicates that one entity serves as the material or reactant upon which another entity (typically an enzyme or process) acts in a chemical or biochemical reaction.
-
E.
targetSubstanceProperty
Indicates that a particular property or characteristic is being ascribed to, measured for, or associated with a specified target substance.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b357d1108190802bc29e0ed7f097 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:49 p.m.