Triple
T9495991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Development Bank |
E229004
|
entity |
| Predicate | lendingInstrument |
P46601
|
FINISHED |
| Object | sovereign loans |
—
|
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: sovereign loans | Statement: [New Development Bank, lendingInstrument, sovereign loans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lendingInstrument Context triple: [New Development Bank, lendingInstrument, sovereign loans]
-
A.
hasLendingInstrument
chosen
Indicates that an entity possesses or utilizes a specific financial instrument used for lending.
-
B.
lendingArm
Indicates that one entity provides financial support or resources to another, typically in the form of a loan or credit.
-
C.
lenderType
Indicates the classification or category of the lender involved in a lending relationship (e.g., bank, individual, institution).
-
D.
lender
Indicates a relationship where one party provides something, typically money or resources, to another with the expectation of repayment or return.
-
E.
loanType
Indicates the specific category or kind of loan associated with an entity or transaction.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95eb87b081908fc7255598cd9a24 |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.