Triple
T21189649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agricultural Risk Coverage program |
E522177
|
entity |
| Predicate | offersChoiceWith |
P143218
|
FINISHED |
| Object | Price Loss Coverage program |
—
|
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: Price Loss Coverage program | Statement: [Agricultural Risk Coverage program, offersChoiceWith, Price Loss Coverage program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersChoiceWith Context triple: [Agricultural Risk Coverage program, offersChoiceWith, Price Loss Coverage program]
-
A.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
B.
offersInterface
Indicates that one entity provides or exposes a specific interface that another entity can use or interact with.
-
C.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
-
D.
offersConnectionTo
Indicates that one entity provides or enables access, linkage, or connectivity to another entity.
-
E.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:07 p.m.