Triple
T18021155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulmonary veins |
E431118
|
entity |
| Predicate | bloodFlowDirection |
P113696
|
FINISHED |
| Object | From periphery of lungs to heart |
—
|
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: From periphery of lungs to heart | Statement: [Pulmonary veins, bloodFlowDirection, From periphery of lungs to heart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodFlowDirection Context triple: [Pulmonary veins, bloodFlowDirection, From periphery of lungs to heart]
-
A.
hasDirectionOfFlow
chosen
Indicates that something moves or is transmitted from one entity or location toward another along a specific path or orientation.
-
B.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
C.
pilgrimFlowDirection
Indicates the direction in which pilgrims move or travel along a route, path, or within a pilgrimage site.
-
D.
vascularFeature
Indicates a relationship where one entity has, exhibits, or is characterized by a particular vascular structure or property.
-
E.
waterwayDirection
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
- 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_69e4b9c299c48190b0cceecf77cb6de9 |
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.