Triple
T21189710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Price Loss Coverage program |
E522178
|
entity |
| Predicate | referencePriceType |
P15883
|
FINISHED |
| Object | statutory reference price |
—
|
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: statutory reference price | Statement: [Price Loss Coverage program, referencePriceType, statutory reference price]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencePriceType Context triple: [Price Loss Coverage program, referencePriceType, statutory reference price]
-
A.
priceReference
chosen
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
-
B.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
-
C.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
D.
priceInfluencedBy
Indicates that the price of one entity is affected or determined by another specified factor or entity.
-
E.
definesPriceFor
Indicates that one entity specifies or establishes the price applicable 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.