Triple
T11651045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BKS |
E276903
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | securities identifier |
C4624
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: securities identifier Context triple: [BKS, instanceOf, securities identifier]
-
A.
International Securities Identification Number
chosen
An International Securities Identification Number (ISIN) is a globally recognized 12-character alphanumeric code that uniquely identifies a specific securities issue, such as a stock or bond, across international markets.
-
B.
financial market identifier registry
A financial market identifier registry is a centralized system that assigns, maintains, and provides standardized unique identifiers for financial markets, venues, and related entities to support accurate reference, trading, and regulatory reporting.
-
C.
Market Identifier Code
A Market Identifier Code (MIC) is a standardized four-character code used to uniquely identify securities trading venues such as exchanges, trading platforms, and markets worldwide.
-
D.
cryptography identifier
A cryptography identifier is a unique label or reference used to distinguish and manage specific cryptographic elements such as keys, algorithms, certificates, or protocols within a security system.
-
E.
securities industry registration database
A securities industry registration database is a centralized system that stores, tracks, and manages registration, licensing, and regulatory information for firms and individuals participating in the securities markets.
- F. None of above.
Provenance (1 batch)
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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.