Triple
T4200543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015–2016 Zika virus outbreak |
E86053
|
entity |
| Predicate | primaryTransmissionRoute |
P52267
|
FINISHED |
| Object | mosquito bites |
—
|
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: mosquito bites | Statement: [2015–2016 Zika virus outbreak, primaryTransmissionRoute, mosquito bites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTransmissionRoute Context triple: [2015–2016 Zika virus outbreak, primaryTransmissionRoute, mosquito bites]
-
A.
primaryTransport
Indicates that one entity serves as the main or most commonly used means of transportation for another entity.
-
B.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
C.
primaryInfectionStructure
Indicates the structure that serves as the main or initial means by which an infection is established in a host.
-
D.
routeOfExposure
chosen
Indicates the pathway or method by which an agent, substance, or factor comes into contact with or enters an organism or system.
-
E.
primaryBus
Indicates that one entity functions as the main or principal bus associated with another entity within a system or configuration.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0363bbb8819093f396afe91972e2 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.