Triple
T38209668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nomura Holdings (Asia-Pacific and European operations) |
E1010503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial services company unit |
C51700
|
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 services company unit Context triple: [Nomura Holdings (Asia-Pacific and European operations), instanceOf, financial services company unit]
-
A.
financial services company division
chosen
A financial services company division is an organizational unit within a financial institution that focuses on a specific set of products, markets, or client segments, managing related operations, risk, and profitability.
-
B.
financial entity
A financial entity is an organization or individual that manages, invests, or transacts money and financial instruments within the economic system.
-
C.
financial institution
A financial institution is an organization that manages money and financial services, such as accepting deposits, providing loans, facilitating investments, and enabling payment transactions for individuals, businesses, and governments.
-
D.
financial center
A financial center is a geographic area or hub where a high concentration of financial institutions, markets, and services are located, facilitating large-scale capital flows, investment, and economic activity.
-
E.
financial service
A financial service is a professional activity or product provided by institutions to help individuals or organizations manage, invest, protect, or transfer money and financial assets.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.