Triple
T5516437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taenia solium |
E144693
|
entity |
| Predicate | ICD10AssociatedCode |
P58680
|
FINISHED |
| Object | B68.0 |
—
|
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: B68.0 | Statement: [Taenia solium, ICD10AssociatedCode, B68.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ICD10AssociatedCode Context triple: [Taenia solium, ICD10AssociatedCode, B68.0]
-
A.
hasICD10Code
chosen
Indicates that an entity is associated with a specific ICD-10 diagnostic code used for classifying diseases and health conditions.
-
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.
relatedCode
Indicates that one code is associated with, linked to, or otherwise contextually connected to another code.
-
E.
regionCodeSystem
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5e8ce08190b7f5f2131bebcd4f |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.