Triple
T1975661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alternative Investment Market |
E42904
|
entity |
| Predicate | typicalInvestorProfile |
P29189
|
FINISHED |
| Object | institutional 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: institutional investors | Statement: [Alternative Investment Market, typicalInvestorProfile, institutional investors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInvestorProfile Context triple: [Alternative Investment Market, typicalInvestorProfile, institutional investors]
-
A.
typeOfInvestor
chosen
Indicates the kind or category of investor that a given entity is classified as.
-
B.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
vestmentStyle
Indicates the style or type of clothing or ceremonial garments associated with an entity.
-
D.
typicalHoldingsType
Indicates the usual or most common category of holdings associated with an entity or account.
-
E.
riskProfile
Indicates the level and characteristics of potential risk associated with an entity, action, or situation.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f835108190b0709ccf3a487a96 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.