Triple
T8494817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPCE |
E201070
|
entity |
| Predicate | hasUnderlyingRiskProfile |
P3672
|
FINISHED |
| Object | high-risk growth stock |
—
|
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: high-risk growth stock | Statement: [SPCE, hasUnderlyingRiskProfile, high-risk growth stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingRiskProfile Context triple: [SPCE, hasUnderlyingRiskProfile, high-risk growth stock]
-
A.
riskReturnProfile
Indicates how the level of risk associated with an entity or investment corresponds to its expected or historical return.
-
B.
riskProfile
chosen
Indicates the level and characteristics of potential risk associated with an entity, action, or situation.
-
C.
hasUnderlyingLEI
Indicates that an entity is associated with, or identified by, a specific underlying Legal Entity Identifier (LEI).
-
D.
hasUnderlyingIssuer
Indicates that one entity serves as the fundamental or primary issuer behind another entity, such as a financial instrument or structured product.
-
E.
hasWithdrawalRisk
Indicates that discontinuing or reducing something is associated with a risk of withdrawal effects or adverse reactions.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57c01f881908cb77c8c834ac08d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.