Triple
T21189683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Price Loss Coverage program |
E522178
|
entity |
| Predicate | includesCommodity |
P86421
|
FINISHED |
| Object | corn |
—
|
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: corn | Statement: [Price Loss Coverage program, includesCommodity, corn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCommodity Context triple: [Price Loss Coverage program, includesCommodity, corn]
-
A.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
B.
mentionsCommodity
Indicates that one entity refers to, cites, or brings up a particular commodity in some form of content or communication.
-
C.
hasMarketCommodity
chosen
Indicates that an entity is associated with or trades in a particular commodity within a market context.
-
D.
commodityClass
Indicates that one entity is classified as belonging to a particular category or class of commodities in relation to another entity.
-
E.
commodity
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733350e588190a31467758a8afa5c |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.