Triple
T18020777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Right ventricle |
E431110
|
entity |
| Predicate | diseaseAssociatedWith |
P76100
|
FINISHED |
| Object | right ventricular failure |
—
|
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: right ventricular failure | Statement: [Right ventricle, diseaseAssociatedWith, right ventricular failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diseaseAssociatedWith Context triple: [Right ventricle, diseaseAssociatedWith, right ventricular failure]
-
A.
hasAssociatedDisease
chosen
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
B.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
C.
associatedDiseaseAgentType
Indicates the type or category of disease-causing agent that is associated with a given disease or condition.
-
D.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
E.
humanDisease
Indicates that the subject is a disease that affects humans.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c1c5f88190a059ce4f86f7ed36 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.