Triple
T18154275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulmonary valve |
E434587
|
entity |
| Predicate | preventsBackflowTo |
P17548
|
FINISHED |
| Object | right ventricle |
—
|
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 ventricle | Statement: [Pulmonary valve, preventsBackflowTo, right ventricle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preventsBackflowTo Context triple: [Pulmonary valve, preventsBackflowTo, right ventricle]
-
A.
regulatesFlowBetween
Indicates a relationship where one entity controls, directs, or modulates the movement or transfer of something (such as material, energy, or information) between two other entities.
-
B.
inflowTo
Indicates that something (such as a fluid, resource, or quantity) flows or moves into a specified target or destination.
-
C.
designedToAvoid
chosen
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
D.
regulatesOutflowOf
Indicates that one entity controls, modulates, or governs the rate or amount of outflow from another entity.
-
E.
flowsDownSideOf
Indicates that one entity moves or runs downward along the side or surface of another entity.
- 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.