Triple
T11864850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winter Fuel Payment |
E282254
|
entity |
| Predicate | typicalPaymentPeriod |
P84192
|
FINISHED |
| Object | November to December |
—
|
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: November to December | Statement: [Winter Fuel Payment, typicalPaymentPeriod, November to December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPaymentPeriod Context triple: [Winter Fuel Payment, typicalPaymentPeriod, November to December]
-
A.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
B.
typicalPeriod
chosen
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
C.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
-
D.
typicalCollectionPeriodStart
Indicates the date or point in time when a standard or customary collection period begins.
-
E.
associatedSettlementPeriod
Indicates a temporal period during which a particular settlement is or was occupied, active, or otherwise relevant.
- 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_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. |
Created at: April 8, 2026, 9:43 p.m.