Triple
T24609008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthribidae |
E609063
|
entity |
| Predicate | pestCommonName |
P156729
|
FINISHED |
| Object | coffee bean weevil |
—
|
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: coffee bean weevil | Statement: [Anthribidae, pestCommonName, coffee bean weevil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pestCommonName Context triple: [Anthribidae, pestCommonName, coffee bean weevil]
-
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.
larvalHostPlantCommonName
Indicates the common name of the plant species that serves as the host for an organism during its larval stage.
-
D.
insectOrderCommonName
Indicates the common (non-scientific) name of the insect order to which an insect belongs.
-
E.
animalCommonNameFeatured
Indicates that a particular animal’s common (vernacular) name is prominently highlighted or used as the primary displayed name in a given context.
- F. None of above. chosen
Provenance (4 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.