Triple
T29178976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leptospira interrogans |
E739694
|
entity |
| Predicate | clinicalManifestationsInHumans |
P62906
|
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: [Leptospira interrogans, clinicalManifestationsInHumans, fever]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinicalManifestationsInHumans Context triple: [Leptospira interrogans, clinicalManifestationsInHumans, fever]
-
A.
humanDisease
Indicates that the subject is a disease that affects humans.
-
B.
manifestationsInclude
chosen
Indicates that one entity’s manifestations or concrete expressions contain or encompass those of another entity.
-
C.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
D.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
E.
clinicalCondition
Indicates that one entity has, exhibits, or is associated with a particular medical or health-related condition described by the other entity.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66343216c81909f1a6503d1538608 |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:56 a.m.