Triple
T34223946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DEO |
E877996
|
entity |
| Predicate | hasUnderlyingFIGI |
P5719
|
FINISHED |
| Object | BBG000C0G2N3 |
—
|
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: BBG000C0G2N3 | Statement: [DEO, hasUnderlyingFIGI, BBG000C0G2N3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingFIGI Context triple: [DEO, hasUnderlyingFIGI, BBG000C0G2N3]
-
A.
hasFIGI
chosen
Indicates that an entity is associated with a specific Financial Instrument Global Identifier (FIGI) that uniquely identifies a financial instrument.
-
B.
hasUnderlyingLEI
Indicates that an entity is associated with, or identified by, a specific underlying Legal Entity Identifier (LEI).
-
C.
hasUnderlyingMarket
Indicates that one entity is based on, derives its value from, or is traded with reference to another entity that serves as its fundamental market.
-
D.
underlyingInstrument
Indicates that one financial instrument serves as the reference or basis for the value, payoff, or structure of another financial instrument.
-
E.
hasUnderlyingSector
Indicates that one entity is fundamentally based in, categorized within, or primarily associated with a particular economic or industry sector.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:55 a.m.