Triple
T10978307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDIC insurance limit |
E259429
|
entity |
| Predicate | amountEffectiveSince |
P26568
|
FINISHED |
| Object | 2008-10-03 |
—
|
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: 2008-10-03 | Statement: [FDIC insurance limit, amountEffectiveSince, 2008-10-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amountEffectiveSince Context triple: [FDIC insurance limit, amountEffectiveSince, 2008-10-03]
-
A.
effectiveForPaymentsMadeAfter
Indicates that a condition, rule, or agreement applies only to payments that are made after a specified time or event.
-
B.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
-
C.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
D.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
-
E.
appliedSince
chosen
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f6a9448190b3932ee801ae0da9 |
completed | April 9, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.