Triple
T18021194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior vena cava |
E431119
|
entity |
| Predicate | medialTo |
P86292
|
FINISHED |
| Object | right lung |
—
|
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: right lung | Statement: [Superior vena cava, medialTo, right lung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medialTo Context triple: [Superior vena cava, medialTo, right lung]
-
A.
locatedMedialTo
chosen
Indicates that one entity is positioned toward the midline of the body relative to another entity.
-
B.
mediatedIn
Indicates that an entity acted as an intermediary or facilitator in bringing about, enabling, or influencing another entity or event.
-
C.
medianSection
Indicates that one entity is a median or central segment derived from or associated with another entity, typically representing its middle section.
-
D.
mediatedBetween
Indicates that an entity acted as an intermediary or go-between facilitating interaction, communication, or negotiation between two other entities.
-
E.
mediantKey
Indicates that one musical key functions as the mediant (built on the third scale degree) in relation to another key.
- 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.