Triple

T419544
Position Surface form Disambiguated ID Type / Status
Subject Regulation A E8069 entity
Predicate Tier2Requires P100 FINISHED
Object ongoing periodic reports to the SEC 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: ongoing periodic reports to the SEC | Statement: [Regulation A, Tier2Requires, ongoing periodic reports to the SEC]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: Tier2Requires
Context triple: [Regulation A, Tier2Requires, ongoing periodic reports to the SEC]
  • A. requiresSkill
    Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
  • B. hostRequirement
    Indicates that one entity specifies or imposes necessary conditions or resources that another entity (the host) must provide or satisfy.
  • C. requires chosen
    Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
  • D. teamLevel
    Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
  • E. higherTierAuthority
    Indicates that one entity holds a superior or higher-ranking level of authority or control over 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_69a2e7f1d1bc81909cf2dc9754a3c334 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eebde1d881908fb212bfba9d7c67 completed Feb. 28, 2026, 1:33 p.m.
PD Predicate disambiguation batch_69a2edd3b948819097d96c73d0a0f699 completed Feb. 28, 2026, 1:29 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.