Triple
T28328317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSE Composite Index |
E717469
|
entity |
| Predicate | primaryExchangeCode |
P201840
|
FINISHED |
| Object | XSHG |
—
|
NE NERFINISHED |
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: XSHG | Statement: [SSE Composite Index, primaryExchangeCode, XSHG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryExchangeCode Context triple: [SSE Composite Index, primaryExchangeCode, XSHG]
-
A.
primaryExchange
Indicates the main or most significant transfer or trade interaction occurring between two parties or systems.
-
B.
primaryExchangeFor
Indicates that one entity serves as the main or principal exchange platform or marketplace used for trading or transacting another entity.
-
C.
primaryExchangeLocation
Indicates the main place or venue where the exchange or transaction between the related entities primarily occurs.
-
D.
primaryCode
Indicates that the referenced code is the main or most authoritative code associated with an entity, as opposed to any secondary or alternative codes.
-
E.
hasPrimaryExchangeCountryCode
Indicates the country code of the main securities exchange on which an entity is primarily listed or traded.
- F. None of above. chosen
Provenance (4 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_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_6a00296249d48190b2de7af946126eaf |
completed | May 10, 2026, 6:44 a.m. |
Created at: April 28, 2026, 12:30 a.m.