Triple
T8812759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glycine |
E209705
|
entity |
| Predicate | includesDomesticatedCrop |
P39654
|
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: [Glycine, includesDomesticatedCrop, soybean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDomesticatedCrop Context triple: [Glycine, includesDomesticatedCrop, soybean]
-
A.
hasCropSpecies
Indicates that a particular location, field, or agricultural system is associated with or used to cultivate a specified crop species.
-
B.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
C.
isDomesticated
Indicates that an entity has been tamed and bred by humans to live and function under human care or control.
-
D.
containsEdibleCrop
chosen
Indicates that one entity includes within it or has present an edible crop as part of its contents or composition.
-
E.
isCultivated
Indicates that an entity is intentionally grown, managed, or maintained by humans rather than occurring or developing naturally without human intervention.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5feed07881909bbe116ae359346a |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.