Triple
T7909108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guntur Mirchi Yard |
E183651
|
entity |
| Predicate | productFormTraded |
P20517
|
FINISHED |
| Object | sun-dried chilies |
—
|
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: sun-dried chilies | Statement: [Guntur Mirchi Yard, productFormTraded, sun-dried chilies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productFormTraded Context triple: [Guntur Mirchi Yard, productFormTraded, sun-dried chilies]
-
A.
productsTraded
Indicates that one entity exchanges or deals specific goods or commodities with another entity.
-
B.
productForm
chosen
Indicates the specific physical or presentation format in which a product is offered or delivered (e.g., tablet, liquid, package type).
-
C.
tradedTo
Indicates that ownership or contractual rights to an entity (such as a player, asset, or item) were transferred from one party to another, typically as part of an exchange or deal.
-
D.
tradedIn
Indicates that one entity has given up or exchanged another entity, typically as part of a transaction to obtain something else.
-
E.
tradedAsset
Indicates that an entity is the asset or instrument being exchanged in a trade transaction between parties.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a5c85ac81908de2ca387826ea2f |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.