Triple
T15003174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | comes sacrarum largitionum |
E374142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial official |
C16098
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: financial official Context triple: [comes sacrarum largitionum, instanceOf, financial official]
-
A.
financial policymaker
A financial policymaker is an individual or institutional actor responsible for designing, implementing, and adjusting rules and strategies that guide a nation’s or organization’s monetary, fiscal, and regulatory financial systems to achieve economic stability and growth.
-
B.
financial analyst
A financial analyst is a professional who evaluates financial data, market trends, and economic conditions to provide insights and recommendations that support investment decisions and organizational financial planning.
-
C.
financial officer role
chosen
A financial officer role is responsible for overseeing an organization’s financial planning, reporting, and control processes to ensure fiscal health, compliance, and strategic use of resources.
-
D.
financialProfessional
A financialProfessional is an individual or entity with specialized expertise in managing, advising on, or analyzing financial assets, markets, and strategies to help clients achieve their economic goals.
-
E.
finance department
The finance department is the organizational unit responsible for managing a company's financial planning, budgeting, accounting, reporting, and cash flow to ensure fiscal stability and support strategic decision-making.
- F. None of above.
Provenance (1 batch)
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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:54 a.m.