Triple

T27660744
Position Surface form Disambiguated ID Type / Status
Subject Radius Bank E697113 entity
Predicate hasFDICInsurance P40552 FINISHED
Object true 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: true | Statement: [Radius Bank, hasFDICInsurance, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFDICInsurance
Context triple: [Radius Bank, hasFDICInsurance, true]
  • A. isFDICInsured chosen
    Indicates that a financial institution or account is covered by insurance from the Federal Deposit Insurance Corporation (FDIC), protecting deposits up to the insured limits.
  • B. typeOfDepositInsurance
    Indicates the specific kind or category of deposit insurance that applies to a financial account or institution.
  • C. hasFinancialInstitution
    Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
  • D. hasFederalReserveBank
    Indicates that an entity possesses, is served by, or is associated with a specific Federal Reserve Bank within the Federal Reserve System.
  • E. hasBankingLicense
    Indicates that an entity is authorized by a regulatory authority to provide banking services under an official license.
  • 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_69ef590b85a4819083ec7c12bd3c9c10 completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f634a016b08190973fd3a552a9757c completed May 2, 2026, 5:30 p.m.
PD Predicate disambiguation batch_69f62c1a92648190835a2c5250d8c758 completed May 2, 2026, 4:53 p.m.
Created at: April 27, 2026, 2:36 p.m.