Triple
T15240984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Set For Life |
E364252
|
entity |
| Predicate | payoutTiming |
P2796
|
FINISHED |
| Object | over an extended period |
—
|
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: over an extended period | Statement: [Set For Life, payoutTiming, over an extended period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payoutTiming Context triple: [Set For Life, payoutTiming, over an extended period]
-
A.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
-
B.
associatedSettlementPeriod
Indicates a temporal period during which a particular settlement is or was occupied, active, or otherwise relevant.
-
C.
commitmentTiming
chosen
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
-
D.
disbursementOption
Indicates the method or arrangement by which funds are paid out or distributed.
-
E.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007db9a148190aadea8d5f8b6b261 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.