Triple
T8150857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Stock Exchange |
E190328
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SSE |
E190328
|
NE 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: SSE | Statement: [Shanghai Stock Exchange, abbreviation, SSE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SSE Context triple: [Shanghai Stock Exchange, abbreviation, SSE]
-
A.
SSE
SSE is the abbreviation for the Santiago Stock Exchange, the main securities exchange in Chile.
-
B.
SSE
chosen
SSE is the commonly used abbreviation for the Shanghai Stock Exchange, one of the largest stock exchanges in the world and a major financial hub in China.
-
C.
SSE
SSE is a major UK-based energy company known for generating, transmitting, distributing, and supplying electricity and gas, particularly in Scotland and Ireland.
-
D.
SSE
SSE (Streaming SIMD Extensions) is an Intel processor instruction set extension that accelerates multimedia, floating-point, and parallel data processing operations.
-
E.
SSE
SSE is the commonly used abbreviation for Sharks Sports & Entertainment, the company that owns and operates the NHL’s San Jose Sharks and related sports and entertainment properties.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbeef189081909f45b8d2aea74225 |
completed | April 1, 2026, 6:45 a.m. |
Created at: March 30, 2026, 5:37 p.m.