Triple
T17584077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khanpur |
E428273
|
entity |
| Predicate | agriculturalProductsTraded |
P75269
|
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: [Khanpur, agriculturalProductsTraded, sugarcane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agriculturalProductsTraded Context triple: [Khanpur, agriculturalProductsTraded, sugarcane]
-
A.
haveAgriculturalTrade
Indicates that there is an ongoing exchange of agricultural goods or services between the related entities.
-
B.
agriculturalProduce
chosen
Indicates that one entity is an agricultural product (such as crops or livestock-derived goods) produced by or associated with another entity.
-
C.
commodityProduced
Indicates that a particular commodity is generated, manufactured, or otherwise produced by a specified entity or process.
-
D.
traditionalAgriculturalProduct
Indicates that something is recognized as an agricultural product produced using long-established, customary methods and practices.
-
E.
productsTraded
Indicates that one entity exchanges or deals specific goods or commodities with another entity.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463d015fc8190b2dd897026d6fcb5 |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.