Triple
T3731898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharchop |
E79083
|
entity |
| Predicate | cultivatesCrop |
P37212
|
FINISHED |
| Object | maize |
—
|
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: maize | Statement: [Sharchop, cultivatesCrop, maize]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultivatesCrop Context triple: [Sharchop, cultivatesCrop, maize]
-
A.
isCultivatedAs
chosen
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
-
B.
cultivatedFor
Indicates that one entity is intentionally grown, raised, or developed for the benefit, use, or purpose of another entity.
-
C.
crop
Indicates the action of cutting or trimming part of an object or image, typically to remove unwanted outer areas while keeping a selected region.
-
D.
cultivationStatus
Indicates the current state or condition of an entity with respect to being cultivated, such as whether and how it is actively grown or managed.
-
E.
cultivationRequirement
Indicates the specific conditions or resources that must be met or provided for something to be successfully 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb21002c81908438170ed6f6c271 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.