Triple
T16400130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PNB Housing Finance Limited |
E398288
|
entity |
| Predicate | targetUseOfFunds |
P36498
|
FINISHED |
| Object | Purchase of residential property |
—
|
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: Purchase of residential property | Statement: [PNB Housing Finance Limited, targetUseOfFunds, Purchase of residential property]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUseOfFunds Context triple: [PNB Housing Finance Limited, targetUseOfFunds, Purchase of residential property]
-
A.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
B.
excludedUseOfFundsFor
Indicates that certain funds are prohibited from being used for a specified purpose or activity.
-
C.
fundingFocus
Indicates that one entity’s funding is directed toward or prioritized for a particular target, theme, or area of activity.
-
D.
fundingObjective
chosen
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
-
E.
additionalFundingPurpose
Indicates the specific reason or intended use for which additional funding is sought or allocated beyond the original amount.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cea4e481908400b852a5a7032a |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.