Triple
T18154291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulmonary valve |
E434587
|
entity |
| Predicate | hasClinicalCondition |
P129457
|
FINISHED |
| Object | pulmonary valve stenosis |
—
|
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: pulmonary valve stenosis | Statement: [Pulmonary valve, hasClinicalCondition, pulmonary valve stenosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClinicalCondition Context triple: [Pulmonary valve, hasClinicalCondition, pulmonary valve stenosis]
-
A.
clinicalCondition
chosen
Indicates that one entity has, exhibits, or is associated with a particular medical or health-related condition described by the other entity.
-
B.
hasAssociatedDisease
Indicates that an entity is linked to, or commonly occurs with, a particular disease or medical condition.
-
C.
hadCondition
Indicates that an entity experienced or was diagnosed with a particular medical or health-related condition.
-
D.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
E.
hasTypicalConditions
Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de3a99c081908e9615072e62b02f |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.