Triple
T17638823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancylostoma caninum |
E429168
|
entity |
| Predicate | canCauseInHumans |
P11983
|
FINISHED |
| Object | eosinophilic enteritis |
—
|
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: eosinophilic enteritis | Statement: [Ancylostoma caninum, canCauseInHumans, eosinophilic enteritis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCauseInHumans Context triple: [Ancylostoma caninum, canCauseInHumans, eosinophilic enteritis]
-
A.
pathogenicityToHumans
chosen
Indicates that an entity has the capacity to cause disease or harmful health effects in humans.
-
B.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
C.
zoonoticPotential
Indicates the potential for a disease or pathogen to be transmitted from animals to humans.
-
D.
transmissionBetweenHumans
Indicates that something (such as a disease, information, or influence) is passed directly from one human to another.
-
E.
includesSpeciesCausing
Indicates that one entity contains or encompasses species that are responsible for causing a particular effect, condition, or outcome in another 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de2c85c819087e17a9ff93e4964 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:01 a.m.