Triple
T18154273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulmonary valve |
E434587
|
entity |
| Predicate | controlsBloodFlowTo |
P20749
|
FINISHED |
| Object | pulmonary artery |
—
|
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 artery | Statement: [Pulmonary valve, controlsBloodFlowTo, pulmonary artery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsBloodFlowTo Context triple: [Pulmonary valve, controlsBloodFlowTo, pulmonary artery]
-
A.
bloodFlowsThrough
Indicates that blood moves within or along the interior of a specified anatomical structure or pathway.
-
B.
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.
-
C.
regulatesOutflowOf
chosen
Indicates that one entity controls, modulates, or governs the rate or amount of outflow from another entity.
-
D.
transportsBloodTo
Indicates that one entity carries or conveys blood from itself or another source to a specified destination entity.
-
E.
pumpsBloodTo
Indicates that one entity circulates or transfers blood to another entity as part of a biological or mechanical flow system.
- 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.