Triple
T17268975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Market Access Program |
E419202
|
entity |
| Predicate | annualFundingCeilingUSD |
P37671
|
FINISHED |
| Object | 200000000 |
—
|
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: 200000000 | Statement: [Market Access Program, annualFundingCeilingUSD, 200000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annualFundingCeilingUSD Context triple: [Market Access Program, annualFundingCeilingUSD, 200000000]
-
A.
peakAnnualFunding
Indicates the maximum amount of funding an entity receives in a single year within a given period.
-
B.
fundingCapType
Indicates the classification or category of a limit placed on the amount of funding that can be provided.
-
C.
maximumGrantAmount
chosen
Indicates the highest monetary value that can be awarded or granted under a specific grant, program, or agreement.
-
D.
fundingLevel
Indicates the amount or degree of financial resources allocated or committed to an entity, project, or activity.
-
E.
subjectToAnnualCap
Indicates that the related amount, usage, or activity is limited by a maximum allowable value that applies on an annual basis.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4803b48190894b3bb9a4970602 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.