Triple
T15217130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUSIP |
E363664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial security identifier |
C34196
|
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: financial security identifier Context triple: [CUSIP, instanceOf, financial security identifier]
-
A.
security identifier
chosen
A security identifier is a unique code assigned to a specific financial instrument to distinguish it from all other securities for trading, settlement, and record-keeping purposes.
-
B.
International Securities Identification Number
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.
-
C.
U.S. federal tax identifier
A U.S. federal tax identifier is a unique number assigned by the federal government to individuals or entities for tax reporting, filing, and identification purposes.
-
D.
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.
-
E.
tax identification number
A tax identification number is a unique numeric or alphanumeric code assigned by a government authority to individuals or entities for the purpose of tracking and administering tax obligations.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:11 a.m.