Triple
T3439052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yersinia pestis |
E72523
|
entity |
| Predicate | humanDisease |
P48276
|
FINISHED |
| Object | acute febrile illness |
—
|
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: acute febrile illness | Statement: [Yersinia pestis, humanDisease, acute febrile illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanDisease Context triple: [Yersinia pestis, humanDisease, acute febrile illness]
-
A.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
B.
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.
-
C.
primaryDisease
Indicates that a disease is the main or principal medical condition affecting an entity, as opposed to secondary or comorbid conditions.
-
D.
relatedDiseaseComplex
Indicates that there is a complex or multifaceted disease relationship between the associated entities, often involving multiple conditions, factors, or mechanisms.
-
E.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f6de1481909b789f4b0e1113d3 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.