Triple
T28328147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stock Connect programs |
E717465
|
entity |
| Predicate | riskControlFeature |
P80826
|
FINISHED |
| Object | pre-trade checking |
—
|
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: pre-trade checking | Statement: [Stock Connect programs, riskControlFeature, pre-trade checking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskControlFeature Context triple: [Stock Connect programs, riskControlFeature, pre-trade checking]
-
A.
riskFeature
Indicates that one entity possesses or exhibits a characteristic, condition, or attribute that increases the likelihood or severity of a negative outcome for another entity or situation.
-
B.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
C.
riskManagementMechanism
chosen
Indicates a mechanism, process, or control used to identify, assess, mitigate, or monitor risks associated with an entity or activity.
-
D.
riskMeasure
Indicates a quantitative assessment of the level of risk associated with an entity, event, or situation.
-
E.
riskManagement
Indicates the implementation of strategies and actions to identify, assess, and mitigate potential risks associated with an entity or activity.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6493156c0819085e5d4796ce46b5a |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:30 a.m.