Triple
T13232770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US1667641005 |
E315063
|
entity |
| Predicate | hasFigi |
P5719
|
FINISHED |
| Object | BBG000C2V3D6 |
—
|
LITERAL FINISHED |
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: BBG000C2V3D6 | Statement: [US1667641005, hasFigi, BBG000C2V3D6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFigi Context triple: [US1667641005, hasFigi, BBG000C2V3D6]
-
A.
hasFIGI
chosen
Indicates that an entity is associated with a specific Financial Instrument Global Identifier (FIGI) that uniquely identifies a financial instrument.
-
B.
fundingInstrument
Indicates that one entity serves as the financial source, mechanism, or tool used to provide funding for another entity or activity.
-
C.
hasFinancialInstrumentType
Indicates that an entity is associated with, or classified by, a specific type or category of financial instrument.
-
D.
isFiatCurrency
Indicates that something is a government-issued currency not backed by a physical commodity but by legal authority and public trust.
-
E.
FISCode
Indicates a standardized financial institution identifier code used to uniquely reference a specific bank or financial entity in transactions or records.
- F. None of above.
Provenance (3 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d34ff288190bdb550a019b7a470 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.