Triple
T31762106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUMICAP |
E810707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | market data identifier |
C38320
|
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: market data identifier Context triple: [RUMICAP, instanceOf, market data identifier]
-
A.
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.
-
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.
financial data vendor
A financial data vendor is an entity that collects, processes, and distributes financial market and economic information to clients such as investors, institutions, and analysts for decision-making and analysis.
-
D.
financial identifier
chosen
A financial identifier is a standardized code or label used to uniquely distinguish a financial entity, instrument, account, or transaction within financial systems.
-
E.
financial data vendor code
A financial data vendor code is a unique identifier assigned by a data provider to represent a specific financial instrument, entity, or data feed within their information systems.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:31 p.m.