Triple
T16267823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acanthocephala |
E394916
|
entity |
| Predicate | parasiticIn |
P19654
|
FINISHED |
| Object | intestinal tract of hosts |
—
|
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: intestinal tract of hosts | Statement: [Acanthocephala, parasiticIn, intestinal tract of hosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parasiticIn Context triple: [Acanthocephala, parasiticIn, intestinal tract of hosts]
-
A.
parasitizes
chosen
Indicates a relationship in which one organism lives on or in another organism, deriving nutrients or benefits at the host’s expense.
-
B.
includesParasiticTaxa
Indicates that the referenced group or set contains taxa that live parasitically on or within other organisms.
-
C.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
D.
speciesInGuise
Indicates that an entity is currently appearing or acting under the guise or form of a particular species, which may differ from its true species.
-
E.
notablePest
Indicates that an entity is recognized as a significant or impactful pest, typically causing notable harm, damage, or nuisance.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c963ec8190b059fecac6248cd9 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.