Triple
T2579285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form D |
E57050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SEC 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: SEC form Context triple: [Form D, instanceOf, SEC form]
-
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.
IRS tax form
An IRS tax form is an official document used by individuals or entities to report financial information to the Internal Revenue Service for the purpose of calculating and paying federal taxes.
-
D.
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.
-
E.
organizational unit of the U.S. Securities and Exchange Commission
An organizational unit of the U.S. Securities and Exchange Commission is a distinct internal division, office, or program area with defined responsibilities, authority, and resources for carrying out specific aspects of the SEC’s regulatory, enforcement, or administrative mission.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:49 p.m.