Triple
T14271893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendra virus |
E353805
|
entity |
| Predicate | transmissionToHumans |
P74969
|
FINISHED |
| Object | primarily via infected horses |
—
|
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: primarily via infected horses | Statement: [Hendra virus, transmissionToHumans, primarily via infected horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionToHumans Context triple: [Hendra virus, transmissionToHumans, primarily via infected horses]
-
A.
transmissionBetweenHumans
Indicates that something (such as a disease, information, or influence) is passed directly from one human to another.
-
B.
pathogenicityToHumans
Indicates that an entity has the capacity to cause disease or harmful health effects in humans.
-
C.
modeOfTransmission
chosen
Indicates the method or pathway through which something, typically a disease or information, is passed from one source to another.
-
D.
plagueTransmission
Indicates the way in which plague is passed or spread from one host, vector, or environment to another.
-
E.
infectionMethod
Indicates the way or mechanism by which an infection is transmitted or established from a source to a host.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de65811d7c8190b075909a6570d415 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.