Triple
T38561124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tularemia |
E928077
|
entity |
| Predicate | hasClinicalForm |
P66791
|
FINISHED |
| Object | ulceroglandular tularemia |
—
|
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: ulceroglandular tularemia | Statement: [tularemia, hasClinicalForm, ulceroglandular tularemia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClinicalForm Context triple: [tularemia, hasClinicalForm, ulceroglandular tularemia]
-
A.
clinicalForm
chosen
Indicates the specific clinical manifestation or presentation type associated with a medical condition or case.
-
B.
hasClinicalAssessment
Indicates that a subject is associated with, or has undergone, a specific clinical assessment or evaluation.
-
C.
hasClinicalBase
Indicates that one entity serves as the clinical foundation, setting, or primary site upon which another entity (such as a study, program, or service) is based or conducted.
-
D.
hasPracticeForm
Indicates that an entity is associated with, or takes place in, a particular form or mode of practice.
-
E.
hasClinicalService
Indicates that an entity provides, offers, or is associated with a specific clinical service.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:32 p.m.