Triple
T8150707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-shares |
E190324
|
entity |
| Predicate | typicalTradingMethod |
P4033
|
FINISHED |
| Object | order-driven continuous auction |
—
|
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: order-driven continuous auction | Statement: [A-shares, typicalTradingMethod, order-driven continuous auction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTradingMethod Context triple: [A-shares, typicalTradingMethod, order-driven continuous auction]
-
A.
tradingApproach
Indicates the method or strategy an entity uses to conduct trading activities or make trade-related decisions.
-
B.
actualTrading
Indicates the occurrence of real, executed trading activity between parties, as opposed to planned, simulated, or potential trades.
-
C.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
D.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
E.
hasTradingModel
chosen
Indicates that one entity uses, is governed by, or is associated with a particular trading model.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4481f19c8190aeec9bf029ad321b |
completed | March 31, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.