Triple
T15936602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advisory Group |
E386455
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial advisory body |
C655
|
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 advisory body Context triple: [Advisory Group, instanceOf, financial advisory body]
-
A.
financial regulatory coordination body
A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
-
B.
financial regulatory authority
A financial regulatory authority is an organization empowered by law to oversee, supervise, and enforce rules governing financial markets and institutions to ensure stability, integrity, and consumer protection.
-
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.
wealth management provider
A wealth management provider is a financial services entity that offers personalized investment, financial planning, and advisory solutions to help clients grow, preserve, and transfer their wealth.
-
E.
advisory body
chosen
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:53 a.m.