Triple
T28328316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSE Composite Index |
E717469
|
entity |
| Predicate | dataVendorTicker |
P56403
|
FINISHED |
| Object | 000001.SS |
—
|
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: 000001.SS | Statement: [SSE Composite Index, dataVendorTicker, 000001.SS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataVendorTicker Context triple: [SSE Composite Index, dataVendorTicker, 000001.SS]
-
A.
dataVendorSymbol
chosen
Indicates a mapping between a data vendor and the specific symbol or code they use to identify an asset or item.
-
B.
dataVendor
Indicates a relationship where one entity serves as a provider or supplier of data to another entity.
-
C.
dataVendorSymbolType
Indicates the type or category of symbol used by a particular data vendor to identify an instrument or entity.
-
D.
relatedTickerExchange
Indicates a relationship where a financial instrument’s ticker symbol is associated with the specific exchange on which it is listed or traded.
-
E.
underlyingCompanyTicker
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or entity.
- 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.