Triple
T11864864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winter Fuel Payment |
E282254
|
entity |
| Predicate | amountDependsOn |
P101951
|
FINISHED |
| Object | age |
—
|
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: age | Statement: [Winter Fuel Payment, amountDependsOn, age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amountDependsOn Context triple: [Winter Fuel Payment, amountDependsOn, age]
-
A.
collateralRequired
Indicates that a party must provide collateral as a condition or security for an obligation, transaction, or agreement.
-
B.
authorizedBondAmount
Indicates the maximum bond value that has been formally approved or permitted for issuance or use in a given context.
-
C.
requiresBalanceWith
Indicates that one entity’s state, quantity, or action must be countered or matched by another to maintain an overall balance or equilibrium.
-
D.
marginRequirement
Indicates the minimum amount of collateral or equity that must be maintained to support a position or transaction, typically expressed as a percentage of the position’s value.
-
E.
paymentAmount
Indicates the specific monetary value involved in a payment transaction between parties.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73883508190a78b5f4ba4a220df |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.