Triple
T16441700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirurida |
E399315
|
entity |
| Predicate | typicalTransmissionRoute |
P74969
|
FINISHED |
| Object | arthropod bite |
—
|
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: arthropod bite | Statement: [Spirurida, typicalTransmissionRoute, arthropod bite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTransmissionRoute Context triple: [Spirurida, typicalTransmissionRoute, arthropod bite]
-
A.
modeOfTransmission
chosen
Indicates the method or pathway through which something, typically a disease or information, is passed from one source to another.
-
B.
transmissionBetweenHumans
Indicates that something (such as a disease, information, or influence) is passed directly from one human to another.
-
C.
secondaryTransmissionRoute
Indicates a non-primary pathway or mechanism through which something (such as a disease, signal, or influence) is transmitted from one entity to another.
-
D.
plagueTransmission
Indicates the way in which plague is passed or spread from one host, vector, or environment to another.
-
E.
routeOfExposure
Indicates the pathway or method by which an agent, substance, or factor comes into contact with or enters an organism or system.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba91dc48190bc35db60f63d36d3 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.