Triple
T9288948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIM securities |
E223466
|
entity |
| Predicate | typicalInvestorConsideration |
P87436
|
FINISHED |
| Object | higher volatility |
—
|
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: higher volatility | Statement: [AIM securities, typicalInvestorConsideration, higher volatility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInvestorConsideration Context triple: [AIM securities, typicalInvestorConsideration, higher volatility]
-
A.
investorObjective
Indicates that an entity’s goal, preference, or intended outcome in its role as an investor is directed toward another entity or investment.
-
B.
targetInvestorNeed
Indicates that an action, product, or communication is specifically aimed at addressing or fulfilling an investor’s particular needs or requirements.
-
C.
typeOfInvestor
Indicates the kind or category of investor that a given entity is classified as.
-
D.
vestmentStyle
Indicates the style or type of clothing or ceremonial garments associated with an entity.
-
E.
typicalHoldingsType
Indicates the usual or most common category of holdings associated with an entity or account.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0862b34c819097cb7c1777313925 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.