Triple
T2798179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reg A |
E53087
|
entity |
| Predicate | investorTypePermitted |
P29189
|
FINISHED |
| Object | accredited 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: accredited investors | Statement: [Reg A, investorTypePermitted, accredited investors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investorTypePermitted Context triple: [Reg A, investorTypePermitted, accredited investors]
-
A.
typeOfInvestor
chosen
Indicates the kind or category of investor that a given entity is classified as.
-
B.
investorAccess
Indicates that one party has permission or the ability to view, use, or interact with investment-related information, tools, or opportunities associated with another party or resource.
-
C.
investorLimitTier1
Indicates the maximum allowable participation or allocation for investors classified in the first (highest-priority) limit tier.
-
D.
hasPrimaryInvestor
Indicates that an entity has a main or leading investor that provides the primary financial backing or funding.
-
E.
coInvestorsIncluded
Indicates that specified co-investors are included as part of a particular investment, deal, or financial arrangement.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddf204148190a53f3f30d645d94c |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.