Triple
T32392191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUA:IND |
E827700
|
entity |
| Predicate | isUsedForRiskModeling |
P24250
|
FINISHED |
| Object | U.S. equity portfolios |
—
|
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: U.S. equity portfolios | Statement: [RUA:IND, isUsedForRiskModeling, U.S. equity portfolios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedForRiskModeling Context triple: [RUA:IND, isUsedForRiskModeling, U.S. equity portfolios]
-
A.
isUsedForDerivatives
Indicates that something serves as a basis, input, or underlying component for creating or calculating derivatives.
-
B.
viewedAsRiskBy
Indicates that one entity is perceived or considered as a potential risk or threat by another entity.
-
C.
hasRiskStatus
Indicates the level or category of risk currently associated with an entity.
-
D.
riskModel
chosen
Indicates a relationship where an entity serves as or is associated with a model used to assess, quantify, or manage risk for another entity or situation.
-
E.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 12:52 a.m.