Triple
T17638702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strongylida |
E429166
|
entity |
| Predicate | clinicalSign |
P47120
|
FINISHED |
| Object | anemia in infected hosts |
—
|
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: anemia in infected hosts | Statement: [Strongylida, clinicalSign, anemia in infected hosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinicalSign Context triple: [Strongylida, clinicalSign, anemia in infected hosts]
-
A.
clinicalSignOf
chosen
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
B.
clinicalBaseOf
Indicates that one clinical entity serves as the foundational basis or underlying source for another clinical entity (such as a diagnosis, assessment, or decision).
-
C.
hasClinicalSignificance
Indicates that something (such as a finding, variant, or condition) has a meaningful impact or relevance in a clinical or medical context.
-
D.
clinicalContext
Indicates the medical situation, setting, or circumstances under which a clinical finding, observation, or action occurs.
-
E.
medicalEvent
Indicates that a specific health-related occurrence or clinical incident has taken place involving one or more entities.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de2c85c819087e17a9ff93e4964 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6 a.m.