Triple
T24974562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | white pine weevil |
E624981
|
entity |
| Predicate | signOfInfestation |
P157489
|
FINISHED |
| Object | shepherds crook bending of leader |
—
|
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: shepherds crook bending of leader | Statement: [white pine weevil, signOfInfestation, shepherds crook bending of leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signOfInfestation Context triple: [white pine weevil, signOfInfestation, shepherds crook bending of leader]
-
A.
signOfInfestation
chosen
Indicates that one entity serves as evidence or indication that another entity is infested or experiencing an infestation.
-
B.
isPestOf
Indicates that one entity is considered a pest that harms, damages, or otherwise negatively affects another entity.
-
C.
notablePest
Indicates that an entity is recognized as a significant or impactful pest, typically causing notable harm, damage, or nuisance.
-
D.
pestOf
Indicates that one entity acts as a pest to another, typically causing harm, damage, or nuisance to it.
-
E.
isEntomopathogenic
Indicates that an organism causes disease or death specifically in insects.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:01 a.m.