Triple
T108532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDFI Bond Guarantee Program |
E2191
|
entity |
| Predicate | capitalType |
P4851
|
FINISHED |
| Object | long-term debt capital |
—
|
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: long-term debt capital | Statement: [CDFI Bond Guarantee Program, capitalType, long-term debt capital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalType Context triple: [CDFI Bond Guarantee Program, capitalType, long-term debt capital]
-
A.
capital
Indicates that one place serves as the official seat of government or primary administrative center for another political entity.
-
B.
investmentType
chosen
Indicates the specific category or nature of an investment associated with an entity or transaction.
-
C.
primaryAsset
Indicates that one entity is the main or most important asset associated with another entity.
-
D.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
E.
notableAsset
Indicates that an entity possesses or is associated with an asset that is particularly significant, prominent, or noteworthy in relation to it.
- 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.