Triple
T1321199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baramati |
E28220
|
entity |
| Predicate | hasCrop |
P13242
|
FINISHED |
| Object | sugarcane |
—
|
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: sugarcane | Statement: [Baramati, hasCrop, sugarcane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrop Context triple: [Baramati, hasCrop, sugarcane]
-
A.
includesCrop
chosen
Indicates that one entity (such as a field, farm, or agricultural area) contains or has within it a specified crop.
-
B.
introducedCrop
Indicates that an entity brought a crop species into a new area or context where it was not previously present or cultivated.
-
C.
hasCultivar
Indicates that one entity is a plant species or variety that possesses, includes, or is associated with a specific cultivated variety (cultivar) as another entity.
-
D.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
E.
hasCanopy
Indicates that one entity possesses or is characterized by a canopy associated with it.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19932888190a3d45871e84f112e |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.