Triple

T1975690
Position Surface form Disambiguated ID Type / Status
Subject Professional Securities Market E42905 entity
Predicate regulatoryAudience P32985 FINISHED
Object qualified investors 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: qualified investors | Statement: [Professional Securities Market, regulatoryAudience, qualified investors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatoryAudience
Context triple: [Professional Securities Market, regulatoryAudience, qualified investors]
  • A. regulatoryType
    Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
  • B. regulatoryDomain
    Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
  • C. 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.
  • D. allowsRegulationOf
    Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
  • E. regulatoryDocument
    Indicates a relationship where one entity serves as a regulatory document that defines rules, standards, or requirements governing another entity.
  • F. None of above. chosen

Provenance (4 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_69a8871289048190b00b0d7744b7b2b1 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb3f835108190b0709ccf3a487a96 completed March 7, 2026, 5:13 a.m.
PD Predicate disambiguation batch_69abaff9a09c8190a81fa13f4b85bc79 completed March 7, 2026, 4:56 a.m.
PDg Predicate description generation batch_69abb09b27e88190bff164040fef6d7e completed March 7, 2026, 4:59 a.m.
Created at: March 4, 2026, 7:36 p.m.