Triple
T18021131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulmonary veins |
E431118
|
entity |
| Predicate | drain |
P87103
|
FINISHED |
| Object | Pulmonary capillary beds |
—
|
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 capillary beds | Statement: [Pulmonary veins, drain, Pulmonary capillary beds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drain Context triple: [Pulmonary veins, drain, Pulmonary capillary beds]
-
A.
drainsPartOf
chosen
Indicates that one entity carries off or removes liquid or fluid from a specific part or portion of another entity.
-
B.
drainsAreaOf
Indicates that one entity serves as a drainage outlet or basin for another entity, carrying away its surface or groundwater.
-
C.
drainedFrom
Indicates that a substance, resource, or liquid has been removed or emptied out from a particular source or container.
-
D.
drainageBetween
Indicates that one area or feature serves as a drainage path or channel between two other areas or features, allowing water or runoff to flow from one to the other.
-
E.
drainageOutlet
Indicates that one entity serves as the point where fluids or runoff are discharged or exit from 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_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.