Triple
T10978338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDIC insurance limit |
E259429
|
entity |
| Predicate | appliesToDepositorType |
P89928
|
FINISHED |
| Object | individuals |
—
|
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: individuals | Statement: [FDIC insurance limit, appliesToDepositorType, individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToDepositorType Context triple: [FDIC insurance limit, appliesToDepositorType, individuals]
-
A.
appliesToPartyType
chosen
Indicates that a rule, condition, or attribute is relevant to and affects a specific type or category of party (such as an individual, organization, or group).
-
B.
typeOfDeposits
Indicates the specific kinds or categories of deposits associated with an account, entity, or transaction.
-
C.
depositType
Indicates the specific kind or category of deposit associated with an account, transaction, or financial arrangement.
-
D.
depositTypeRecognized
Indicates that the type of deposit involved in a transaction or context has been identified and classified as a valid, known category.
-
E.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
- 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.