Triple
T37393021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sequoia Fund |
E928768
|
entity |
| Predicate | investmentRestriction |
P125239
|
FINISHED |
| Object | subject to prospectus limits |
—
|
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: subject to prospectus limits | Statement: [Sequoia Fund, investmentRestriction, subject to prospectus limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investmentRestriction Context triple: [Sequoia Fund, investmentRestriction, subject to prospectus limits]
-
A.
policyRestriction
chosen
Indicates that an entity is subject to a limiting rule, condition, or constraint imposed by a policy.
-
B.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
C.
mayHaveRestriction
Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
-
D.
mandateRestriction
Indicates that an authority imposes a binding limitation or requirement on an entity’s actions or conditions.
-
E.
moneyBillsRestriction
Indicates a limitation or control placed on the use, amount, or handling of money bills in a given context.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.