Triple
T31407313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmand Valley Authority projects |
E801165
|
entity |
| Predicate | developedForCrop |
P54821
|
FINISHED |
| Object | wheat |
—
|
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: wheat | Statement: [Helmand Valley Authority projects, developedForCrop, wheat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedForCrop Context triple: [Helmand Valley Authority projects, developedForCrop, wheat]
-
A.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
-
B.
wasUsedOnCrop
Indicates that something (such as a substance, tool, or method) was applied or utilized on a particular crop.
-
C.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
D.
hasCropSpecies
chosen
Indicates that a particular location, field, or agricultural system is associated with or used to cultivate a specified crop species.
-
E.
introducedCrop
Indicates that an entity brought a crop species into a new area or context where it was not previously present or cultivated.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 30, 2026, 8:33 p.m.