Triple
T5340643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form U4 |
E123935
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | securities industry regulatory form |
C3993
|
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: securities industry regulatory form Context triple: [Form U4, instanceOf, securities industry regulatory form]
-
A.
securities industry registration database
A securities industry registration database is a centralized system that stores, tracks, and manages registration, licensing, and regulatory information for firms and individuals participating in the securities markets.
-
B.
regulatory filing
chosen
A regulatory filing is an official document or set of documents submitted to a government or regulatory authority to report required information, demonstrate compliance, or request approval related to an organization’s activities.
-
C.
securities regulation law
Securities regulation law is the body of rules and principles governing the issuance, trading, disclosure, and oversight of financial instruments such as stocks and bonds to protect investors and maintain fair, efficient markets.
-
D.
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.
-
E.
regulatory reporting platform
A regulatory reporting platform is a system that collects, validates, and transforms organizational data into compliant reports for submission to regulators according to applicable rules and deadlines.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2 p.m.