Triple
T35745498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twelve Patients: Life and Death at Bellevue Hospital |
E1033166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical literature |
C32505
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: medical literature Context triple: [Twelve Patients: Life and Death at Bellevue Hospital, instanceOf, medical literature]
-
A.
medical library
A medical library is a specialized information center that collects, organizes, and provides access to medical and health-related resources to support clinical practice, research, and education.
-
B.
medical text
chosen
A medical text is a written document that presents, explains, or analyzes information related to health, diseases, treatments, or medical science for clinical, educational, or research purposes.
-
C.
medical compendium
A medical compendium is a comprehensive, systematically organized reference work that consolidates medical knowledge, including diseases, treatments, diagnostics, and related scientific information, for use by healthcare professionals and students.
-
D.
medical encyclopedia
A medical encyclopedia is a comprehensive reference work that systematically compiles and explains medical terms, conditions, treatments, and related health information for professionals and the general public.
-
E.
medical author
A medical author is a professional who researches, writes, and edits scientifically accurate and clinically relevant content on medical topics for audiences such as healthcare providers, patients, and the general public.
- F. None of above.
Provenance (1 batch)
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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.