Triple

T4119600
Position Surface form Disambiguated ID Type / Status
Subject Annual Compliance Determination E90378 entity
Predicate instanceOf P0 FINISHED
Object regulatory report C12268 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: regulatory report
Context triple: [Annual Compliance Determination, instanceOf, regulatory report]
  • A. regulatory document chosen
    A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
  • B. 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.
  • C. regulatory filing
    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. government report
    A government report is an official document produced by a public agency that presents findings, data, analyses, or recommendations on matters of public policy, administration, or societal concern.
  • E. classified report
    A classified report is a formal document containing sensitive or restricted information that is protected by specific security protocols and only accessible to authorized individuals.
  • 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_69aed95c080881908125e30c5dcdc6f8 completed March 9, 2026, 2:29 p.m.
Created at: March 9, 2026, 3:41 p.m.