Triple

T419552
Position Surface form Disambiguated ID Type / Status
Subject Regulation A E8069 entity
Predicate investorLimitTier1 P14696 FINISHED
Object no specific investment limit by income or net worth 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: no specific investment limit by income or net worth | Statement: [Regulation A, investorLimitTier1, no specific investment limit by income or net worth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: investorLimitTier1
Context triple: [Regulation A, investorLimitTier1, no specific investment limit by income or net worth]
  • A. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • B. insuranceLimitPerDepositorPerBank
    Indicates the maximum amount of insurance coverage that applies to each individual depositor at each separate bank.
  • C. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • D. eligibleBorrower
    Indicates that an entity meets the required conditions to be allowed to borrow (e.g., money, items, or resources) under a given set of rules or policies.
  • E. limitedSystemType
    Indicates that the system is restricted to a specific subset or category of system types, rather than allowing all possible types.
  • 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_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.
PDg Predicate description generation batch_69a2eeb8545c8190a2b8517e7ed5b92e completed Feb. 28, 2026, 1:33 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.