Triple

T108543
Position Surface form Disambiguated ID Type / Status
Subject CDFI Bond Guarantee Program E2191 entity
Predicate eligibleIssuer P3673 FINISHED
Object qualified issuer 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: qualified issuer | Statement: [CDFI Bond Guarantee Program, eligibleIssuer, qualified issuer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: eligibleIssuer
Context triple: [CDFI Bond Guarantee Program, eligibleIssuer, qualified issuer]
  • A. issuedBy
    Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
  • B. eligibleInstitution chosen
    Indicates that an institution satisfies specified criteria or requirements to qualify for a particular program, benefit, or status.
  • 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. hasBank
    Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
  • E. supportsAddressTypes
    Indicates that an entity is capable of handling or working with one or more specified types of addresses.
  • 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_69a24fcdaeb48190a2d796677e4b3281 completed Feb. 28, 2026, 2:15 a.m.
NER Named-entity recognition batch_69a25a1199ac8190ac65ffaaf45b4f5b completed Feb. 28, 2026, 2:59 a.m.
PD Predicate disambiguation batch_69a2563e7188819091e9a94e071991d7 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:20 a.m.