Triple
T9550364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSCI USA Index |
E230404
|
entity |
| Predicate | liquidityScreening |
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 Index, liquidityScreening, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liquidityScreening Context triple: [MSCI USA Index, liquidityScreening, yes]
-
A.
hasLiquidityCharacteristic
Indicates that one entity possesses or is associated with a particular liquidity-related property or feature in relation to another entity.
-
B.
investabilityScreening
Indicates the process of evaluating an entity or opportunity against defined criteria to determine whether it is suitable or eligible for investment.
-
C.
fundsFlowThrough
Indicates that financial resources are transferred or routed from one entity to another via an intermediate entity, account, or channel.
-
D.
hasScreened
Indicates that one entity has shown, displayed, or evaluated another entity, typically in the context of presenting media or conducting a review or check.
-
E.
screeningBasis
Indicates the underlying reason, criterion, or grounds on which a screening or evaluation is conducted between entities.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9906bc90819086f105c453e63c83 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:02 p.m.