Triple
T4160689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kocher incision |
E91525
|
entity |
| Predicate | providesExposureTo |
P54169
|
FINISHED |
| Object | gallbladder fossa |
—
|
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: gallbladder fossa | Statement: [Kocher incision, providesExposureTo, gallbladder fossa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesExposureTo Context triple: [Kocher incision, providesExposureTo, gallbladder fossa]
-
A.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
B.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
-
D.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
-
E.
exposedDuring
Indicates that something becomes visible, accessible, or subject to influence specifically within a given time period, event, or contextual interval.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0320775c8190b90d80f512060f1c |
completed | March 9, 2026, 5:28 p.m. |
Created at: March 9, 2026, 3:44 p.m.