Triple
T4131912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebola virus disease |
E85058
|
entity |
| Predicate | ICD10 |
P6645
|
FINISHED |
| Object | A98.4 |
—
|
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: A98.4 | Statement: [Ebola virus disease, ICD10, A98.4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ICD10 Context triple: [Ebola virus disease, ICD10, A98.4]
-
A.
relatedCodeSet
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
B.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
C.
diagnoses
Indicates that a medical professional identifies and determines the nature or cause of a condition, disease, or problem in a patient.
-
D.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
E.
diseaseType
chosen
Indicates that one entity is classified as a specific type or category of disease in relation to 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:42 p.m.