Triple
T8150863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Stock Exchange |
E190328
|
entity |
| Predicate | openedForTrading |
P67026
|
FINISHED |
| Object | 1990-12-19 |
—
|
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: 1990-12-19 | Statement: [Shanghai Stock Exchange, openedForTrading, 1990-12-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForTrading Context triple: [Shanghai Stock Exchange, openedForTrading, 1990-12-19]
-
A.
openedForTrade
chosen
Indicates that an entity has begun allowing commercial transactions or trading activities to occur.
-
B.
tradingStatus
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
-
C.
hasTradingHours
Indicates that an entity operates or is available for trading during specified time periods.
-
D.
hasTradingSession
Indicates that an entity participates in or is associated with a specific trading session or period during which trading activities occur.
-
E.
hasPreMarketSession
Indicates that a financial instrument or market has a designated trading session that occurs before the regular market hours.
- 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.