Triple
T22629984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bt cotton |
E558520
|
entity |
| Predicate | effectOnTargetInsects |
P84339
|
FINISHED |
| Object | gut cell lysis and death |
—
|
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: gut cell lysis and death | Statement: [Bt cotton, effectOnTargetInsects, gut cell lysis and death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnTargetInsects Context triple: [Bt cotton, effectOnTargetInsects, gut cell lysis and death]
-
A.
interactionWithInsects
Indicates a relationship where an entity engages in some form of contact, behavior, or exchange involving insects.
-
B.
effectivenessAgainst
chosen
Indicates how well one entity performs in countering, influencing, or mitigating the impact of another entity.
-
C.
notablePest
Indicates that an entity is recognized as a significant or impactful pest, typically causing notable harm, damage, or nuisance.
-
D.
hasStateInsect
Indicates that a state has designated a particular insect as its official state insect.
-
E.
pestManagement
Indicates actions or strategies implemented to prevent, control, or eliminate pests affecting a target 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3febd081909ff21abef1e4035d |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:02 p.m.