Triple
T22629934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roundup Ready crops |
E558519
|
entity |
| Predicate | primaryBenefitClaim |
P25020
|
FINISHED |
| Object | improved weed control |
—
|
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: improved weed control | Statement: [Roundup Ready crops, primaryBenefitClaim, improved weed control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBenefitClaim Context triple: [Roundup Ready crops, primaryBenefitClaim, improved weed control]
-
A.
primaryBenefit
chosen
Indicates that one entity serves as the main or most important advantage, gain, or positive outcome associated with another entity.
-
B.
priorityBenefit
Indicates that one benefit takes precedence over or is considered more important than another in a given context.
-
C.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
D.
primaryBeneficiaries
Indicates which entities are the main recipients or advantaged parties resulting from a particular action, resource, or arrangement.
-
E.
benefitProtection
Indicates that one entity provides protective advantages or safeguards that benefit 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_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.