Triple
T18021193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior vena cava |
E431119
|
entity |
| Predicate | lateralTo |
P86049
|
FINISHED |
| Object | ascending aorta |
—
|
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: ascending aorta | Statement: [Superior vena cava, lateralTo, ascending aorta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lateralTo Context triple: [Superior vena cava, lateralTo, ascending aorta]
-
A.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
-
B.
numberOfLaterals
Indicates the count of lateral branches or side elements associated with a given entity or structure.
-
C.
auxiliaryTo
Indicates that one entity serves as a supporting or helping element that assists or modifies the primary action or role of another entity.
-
D.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
E.
onSide
chosen
Indicates that one entity is positioned along or adjacent to the side 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_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.