Triple
T18565386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form N-1A |
E453748
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mutual fund registration statement |
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: mutual fund registration statement Context triple: [Form N-1A, instanceOf, mutual fund registration statement]
-
A.
structural and investment fund
A structural and investment fund is a pooled financial vehicle designed to provide long-term capital for infrastructure, development, or strategic projects while optimizing risk-return profiles through diversified, often regulated, investment structures.
-
B.
fund
A fund is a pooled collection of financial resources, typically managed by an entity or professional, established for a specific investment, operational, or designated purpose.
-
C.
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.
-
D.
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.
-
E.
exemption from securities registration
Exemption from securities registration is a legal provision that allows certain securities offerings to be sold without undergoing the full registration process with securities regulators, typically when specific conditions or criteria are met.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.