Triple
T34044893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolving Fund Program |
E873059
|
entity |
| Predicate | financialModel |
P178172
|
FINISHED |
| Object | revolving fund model |
—
|
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: revolving fund model | Statement: [Revolving Fund Program, financialModel, revolving fund model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialModel Context triple: [Revolving Fund Program, financialModel, revolving fund model]
-
A.
financialBehavior
Indicates how an entity manages, uses, or responds to money and financial resources in practice.
-
B.
fiancee
Indicates that one person is formally engaged to be married to another person.
-
C.
financialNature
Indicates that the relationship or interaction between entities involves financial aspects, such as money, funding, payments, or economic value.
-
D.
financeScope
Indicates the financial coverage, limits, or extent to which a particular action, agreement, or responsibility applies.
-
E.
mainFinancier
Indicates that one entity serves as the primary provider of financial support or funding for another entity or activity.
- F. None of above. chosen
Provenance (4 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:51 a.m.