Triple
T32670546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Certified Development Company |
E835278
|
entity |
| Predicate | loanProgramComponent |
P32140
|
FINISHED |
| Object | second mortgage financing |
—
|
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: second mortgage financing | Statement: [Certified Development Company, loanProgramComponent, second mortgage financing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loanProgramComponent Context triple: [Certified Development Company, loanProgramComponent, second mortgage financing]
-
A.
loanType
Indicates the specific category or kind of loan associated with an entity or transaction.
-
B.
applicablePrograms
Indicates that certain programs are relevant to, valid for, or can be applied in the context of a given entity or situation.
-
C.
loanSource
Indicates that one entity is the origin or provider of a loan extended to another entity.
-
D.
loanStructure
chosen
Indicates the specific terms, components, and repayment arrangement that define how a loan is organized between parties.
-
E.
initiatedUnderProgram
Indicates that an action or process was started as part of, or in accordance with, a specific program or initiative.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7ac1f288190ab86a6dd0b6491cd |
completed | May 3, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.