Triple

T3050528
Position Surface form Disambiguated ID Type / Status
Subject US20030N1019 E83557 entity
Predicate regulatoryUse P14058 FINISHED
Object securities regulation reporting LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: securities regulation reporting | Statement: [US20030N1019, regulatoryUse, securities regulation reporting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatoryUse
Context triple: [US20030N1019, regulatoryUse, securities regulation reporting]
  • A. regulatesUse
    Indicates that one entity controls, governs, or sets rules for how another entity may be used.
  • B. allowsRegulationOf
    Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
  • C. regulatoryType chosen
    Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
  • D. alsoRegulates
    Indicates that an entity not only has a primary regulatory effect on a target but additionally regulates that same target through another, supplementary regulatory relationship.
  • E. regulatoryStandard
    Indicates that one entity serves as an official rule, guideline, or benchmark that governs, constrains, or evaluates the behavior, quality, or performance of another entity.
  • F. None of above.

Provenance (3 batches)

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_69ad8b24924c8190a9bb6f61d519e4ae completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9bb1a46081908547a2f27cbf3446 completed March 8, 2026, 3:54 p.m.
PD Predicate disambiguation batch_69ad962195388190856013a2519c2b0f completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 3:01 p.m.