Triple
T29020067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opisthosporidia |
E737425
|
entity |
| Predicate | hasHostRange |
P2901
|
FINISHED |
| Object | various eukaryotic 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: various eukaryotic hosts | Statement: [Opisthosporidia, hasHostRange, various eukaryotic hosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostRange Context triple: [Opisthosporidia, hasHostRange, various eukaryotic hosts]
-
A.
hostRange
chosen
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
-
B.
hasHostCharacter
Indicates that one entity serves as the host or primary character associated with another entity, such as a show, event, or media production.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
hasHosts
Indicates that one entity serves as the host or hosting environment for another entity.
-
E.
qualifiedAsHost
Indicates that an entity has met the necessary criteria or standards to serve in the role of 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 28, 2026, 9:48 a.m.