Triple
T16886071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundibugyo ebolavirus |
E421542
|
entity |
| Predicate | clinicalFeature |
P47120
|
FINISHED |
| Object | fever |
—
|
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: fever | Statement: [Bundibugyo ebolavirus, clinicalFeature, fever]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinicalFeature Context triple: [Bundibugyo ebolavirus, clinicalFeature, fever]
-
A.
clinicalSignOf
chosen
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
B.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
C.
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).
-
D.
clinicalForm
Indicates the specific clinical manifestation or presentation type associated with a medical condition or case.
-
E.
pathologyFeature
Indicates that one entity is a pathological characteristic, sign, or abnormal finding associated with another entity in a medical or biological context.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc126e881909dae8133ad34acc9 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.