Triple
T18088078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inferior vena cava |
E432890
|
entity |
| Predicate | vertebralLevelOfCavalOpening |
P130385
|
FINISHED |
| Object | T8 |
—
|
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: T8 | Statement: [Inferior vena cava, vertebralLevelOfCavalOpening, T8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vertebralLevelOfCavalOpening Context triple: [Inferior vena cava, vertebralLevelOfCavalOpening, T8]
-
A.
caudalSpineLocation
Indicates the anatomical position or region where the caudal (tail) spine is located on an organism.
-
B.
vascularFeature
Indicates a relationship where one entity has, exhibits, or is characterized by a particular vascular structure or property.
-
C.
venousDrainage
Indicates that one anatomical structure serves as a pathway for venous blood to drain from another structure or region.
-
D.
verticalLocation
Indicates a vertical positional relationship where one entity is located above or below another along the up-down axis.
-
E.
caveNumber
Indicates a relationship where an entity is assigned or associated with a specific cave identifier or number.
- F. None of above. chosen
Provenance (4 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd16234c8190b547e893a829d6c5 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:27 a.m.