Triple
T4771206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wegener's granulomatosis |
E105929
|
entity |
| Predicate | hasICD10Code |
P58680
|
FINISHED |
| Object | M31.3 |
—
|
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: M31.3 | Statement: [Wegener's granulomatosis, hasICD10Code, M31.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasICD10Code Context triple: [Wegener's granulomatosis, hasICD10Code, M31.3]
-
A.
diagnosedWith
Indicates that a subject has been identified, typically by a medical professional, as having a particular disease or medical condition.
-
B.
relatedCodeSet
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
C.
mayBeComorbidWith
Indicates that two conditions or disorders can occur together in the same individual, potentially influencing each other’s presence or severity.
-
D.
hasATCCode
Indicates that a pharmaceutical product or substance is assigned a specific Anatomical Therapeutic Chemical (ATC) classification code.
-
E.
hasTargetDisease
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655e5dcc8190a932be9b1baaffb2 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:21 p.m.