Triple
T22629898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roundup Ready crops |
E558519
|
entity |
| Predicate | firstCommercialCropType |
P148988
|
FINISHED |
| Object | soybean |
—
|
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: soybean | Statement: [Roundup Ready crops, firstCommercialCropType, soybean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCommercialCropType Context triple: [Roundup Ready crops, firstCommercialCropType, soybean]
-
A.
firstCommercialPlant
Indicates that the subject is the first commercial-scale plant or facility of its kind to be established or operated.
-
B.
majorCrop
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
C.
introducedCrop
Indicates that an entity brought a crop species into a new area or context where it was not previously present or cultivated.
-
D.
cultivatedSpecies
Indicates that one entity is a species that is intentionally grown or cultivated by another entity.
-
E.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:02 p.m.