Triple
T24304204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitophilus zeamais |
E612487
|
entity |
| Predicate | primaryDamage |
P22116
|
FINISHED |
| Object | internal feeding in grain kernels |
—
|
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: internal feeding in grain kernels | Statement: [Sitophilus zeamais, primaryDamage, internal feeding in grain kernels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDamage Context triple: [Sitophilus zeamais, primaryDamage, internal feeding in grain kernels]
-
A.
primaryDamageType
chosen
Indicates the main kind of harm or injury that an action, event, or object is responsible for causing.
-
B.
primaryCombat
Indicates that one entity is the main or principal opponent that another entity engages with in combat.
-
C.
damageBasis
Indicates the underlying reason, cause, or basis on which damage is determined or assessed in a given context.
-
D.
primaryEffect
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
-
E.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29224c7cc8190bd1a32318198326c |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:29 a.m.