Triple
T23710437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beauveria |
E585844
|
entity |
| Predicate | targetPests |
P97582
|
FINISHED |
| Object | agricultural insect pests |
—
|
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: agricultural insect pests | Statement: [Beauveria, targetPests, agricultural insect pests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPests Context triple: [Beauveria, targetPests, agricultural insect pests]
-
A.
notablePest
Indicates that an entity is recognized as a significant or impactful pest, typically causing notable harm, damage, or nuisance.
-
B.
pestManagement
Indicates actions or strategies implemented to prevent, control, or eliminate pests affecting a target entity.
-
C.
typicalTargetSpecies
chosen
Indicates the species that is most commonly or characteristically targeted or affected by a given action, process, or agent.
-
D.
preysOn
Indicates that one entity hunts, kills, and consumes another entity as a food source.
-
E.
predators
Indicates a relationship where one organism hunts, kills, and consumes another organism as a food source.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b776d21c8190af48958e1b14aa4c |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.