Triple
T2918730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eumeninae |
E78667
|
entity |
| Predicate | hostPreference |
P9669
|
FINISHED |
| Object | primarily Lepidoptera larvae |
—
|
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: primarily Lepidoptera larvae | Statement: [Eumeninae, hostPreference, primarily Lepidoptera larvae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostPreference Context triple: [Eumeninae, hostPreference, primarily Lepidoptera larvae]
-
A.
hostSelection
chosen
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
B.
hostSelectionBody
Indicates the body or organization responsible for selecting or appointing the host of an event, activity, or function.
-
C.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
-
D.
isPreferredWhen
Indicates that one option, condition, or entity is chosen or favored over others in a particular context or situation.
-
E.
hostRequirement
Indicates that one entity specifies or imposes necessary conditions or resources that another entity (the host) must provide or satisfy.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:54 p.m.