Triple
T18145187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | $40 a Day |
E434369
|
entity |
| Predicate | dailyBudgetAmount |
P83413
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [$40 a Day, dailyBudgetAmount, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailyBudgetAmount Context triple: [$40 a Day, dailyBudgetAmount, 40]
-
A.
budgetFrom
Indicates that a budget or funding allocation originates from or is provided by a particular source.
-
B.
authorizedSpending
Indicates that an entity has been granted permission to spend or allocate a specified amount of resources, typically funds, under defined conditions.
-
C.
dailyQuota
chosen
Indicates the maximum amount or limit allocated or allowed for an entity within a single day.
-
D.
budgetRight
Indicates that an entity has the authority, responsibility, or entitlement to allocate, manage, or decide on the use of a specified budget or financial resources.
-
E.
authorizedBudget
Indicates that a specified budget amount has been formally approved for use by or for a particular entity or purpose.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de32d3f88190bd9f406729716407 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.