Triple
T12467847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTAB |
E297972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational identifier |
C29047
|
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: organizational identifier Context triple: [MTAB, instanceOf, organizational identifier]
-
A.
identifier management guideline
An identifier management guideline defines standardized rules and best practices for creating, using, maintaining, and retiring unique identifiers to ensure consistency, traceability, and integrity across systems and processes.
-
B.
globally unique identifier
A globally unique identifier is a value, typically a long numeric or alphanumeric string, that is guaranteed (or practically guaranteed) to be unique across all systems, times, and contexts for reliably identifying an entity.
-
C.
cryptography identifier
chosen
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.
-
D.
bibliographic identifier
A bibliographic identifier is a standardized code or string that uniquely distinguishes a specific published or unpublished bibliographic resource within catalogs, databases, or information systems.
-
E.
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.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.