Triple
T31557535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSCI USA Minimum Volatility Index |
E805166
|
entity |
| Predicate | liquidityScreen |
P89752
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MSCI USA Minimum Volatility Index, liquidityScreen, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liquidityScreen Context triple: [MSCI USA Minimum Volatility Index, liquidityScreen, yes]
-
A.
liquidityScreening
chosen
Indicates that an entity is evaluated or filtered based on its ability to meet short-term financial obligations or convert assets to cash (i.e., its liquidity).
-
B.
hasLiquidityCharacteristic
Indicates that one entity possesses or is associated with a particular liquidity-related property or feature in relation to another entity.
-
C.
viewOnLeverage
Indicates a stance or opinion an entity holds regarding the use or level of financial leverage.
-
D.
screensAt
Indicates that one entity shows, projects, or displays another entity (such as a film, program, or content) on a screen or at a screening venue.
-
E.
screenCapacity
Indicates the maximum number of items or content units that can be displayed on a screen at one time.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:13 p.m.