Triple
T19384808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIX:CSGN |
E484905
|
entity |
| Predicate | hadFIGI |
P5719
|
FINISHED |
| Object | BBG000BCSCL8 |
—
|
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: BBG000BCSCL8 | Statement: [SIX:CSGN, hadFIGI, BBG000BCSCL8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFIGI Context triple: [SIX:CSGN, hadFIGI, BBG000BCSCL8]
-
A.
hasFIGI
chosen
Indicates that an entity is associated with a specific Financial Instrument Global Identifier (FIGI) that uniquely identifies a financial instrument.
-
B.
HIPNumber
Indicates that an entity is identified by a specific HIP (Hipparcos) catalog number used for astronomical objects.
-
C.
FISCode
Indicates a standardized financial institution identifier code used to uniquely reference a specific bank or financial entity in transactions or records.
-
D.
FIBACode
Indicates a relationship where an entity is assigned or associated with a specific FIBA (International Basketball Federation) identification code.
-
E.
GNDID
Indicates a standardized authority identifier linking an entity to its unique record in the Gemeinsame Normdatei (GND) authority file.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b3ffa548190a060d6e94562a5d2 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.