Triple
T21958791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biomphalaria alexandrina |
E542264
|
entity |
| Predicate | diseaseTypeTransmitted |
P6645
|
FINISHED |
| Object | parasitic disease |
—
|
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: parasitic disease | Statement: [Biomphalaria alexandrina, diseaseTypeTransmitted, parasitic disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diseaseTypeTransmitted Context triple: [Biomphalaria alexandrina, diseaseTypeTransmitted, parasitic disease]
-
A.
diseaseType
chosen
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
B.
modeOfTransmission
Indicates the method or pathway through which something, typically a disease or information, is passed from one source to another.
-
C.
transmissionBetweenHumans
Indicates that something (such as a disease, information, or influence) is passed directly from one human to another.
-
D.
diseaseVector
Indicates that one entity serves as a carrier or transmitter that spreads a disease-causing agent to another entity.
-
E.
plagueTransmission
Indicates the way in which plague is passed or spread from one host, vector, or environment to another.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1244204f081909742d4fe138610d6 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8 p.m.