Triple
T22629897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roundup Ready crops |
E558519
|
entity |
| Predicate | firstCommercializedIn |
P40835
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Roundup Ready crops, firstCommercializedIn, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCommercializedIn Context triple: [Roundup Ready crops, firstCommercializedIn, 1996]
-
A.
wasFirstCommercializedBy
Indicates that the subject was initially brought to market or made commercially available by the object.
-
B.
firstCommercialUse
Indicates the earliest point in time at which something was used commercially or put into commercial operation.
-
C.
firstCommercialReleaseYear
chosen
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
-
D.
firstCommercialApplication
Indicates that an entity represents the earliest or initial commercial use or deployment of another entity (such as a technology, invention, or product).
-
E.
firstPublicUseYear
Indicates the calendar year in which something was first made available for use by the public.
- 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.