Triple
T17262003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aedes aegypti |
E419029
|
entity |
| Predicate | hostSeekingBehavior |
P9669
|
FINISHED |
| Object | prefers to feed on humans indoors |
—
|
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: prefers to feed on humans indoors | Statement: [Aedes aegypti, hostSeekingBehavior, prefers to feed on humans indoors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSeekingBehavior Context triple: [Aedes aegypti, hostSeekingBehavior, prefers to feed on humans indoors]
-
A.
hostsNearby
Indicates that one entity serves as a host located in close physical proximity to another entity.
-
B.
hostOccupation
Indicates that one entity serves as the primary job, profession, or role held by another entity.
-
C.
hostSelection
chosen
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
D.
seeksLodgingIn
Indicates that one entity is actively trying to obtain or arrange a place to stay within a specified location.
-
E.
hostStarActivityLevel
Indicates the intensity or level of stellar activity exhibited by the host star in the relationship or context described.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e717a348190ae6835fb08f38125 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.