Triple
T5340394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDGAR |
E123930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SEC filing system |
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: SEC filing system Context triple: [EDGAR, instanceOf, SEC filing system]
-
A.
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.
-
B.
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.
-
C.
Treasury securities account system
A Treasury securities account system is a platform that records, manages, and processes the issuance, ownership, transactions, and servicing (e.g., interest and principal payments) of government debt instruments for investors and institutions.
-
D.
industry clearing and settlement system
An industry clearing and settlement system is a centralized infrastructure that validates, nets, and finalizes financial transactions between market participants, ensuring accurate, timely, and risk-managed transfer of funds and securities.
-
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.