Triple
T30945656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto Wucherer |
E788381
|
entity |
| Predicate | associatedWithOrganism |
P184627
|
FINISHED |
| Object | filarial nematodes |
—
|
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: filarial nematodes | Statement: [Otto Wucherer, associatedWithOrganism, filarial nematodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithOrganism Context triple: [Otto Wucherer, associatedWithOrganism, filarial nematodes]
-
A.
hasOrganism
Indicates that one entity is an organism associated with, contained in, or otherwise possessed by another entity.
-
B.
speciesAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between a species and another entity (such as a habitat, condition, or feature), without specifying the exact nature of that relationship.
-
C.
containsOrganismsWith
Indicates that one entity includes or holds within it one or more organisms associated with another entity.
-
D.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
-
E.
includesOrganisms
Indicates that one entity contains, encompasses, or has as members one or more specified organisms.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:53 p.m.