Triple
T19384818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIX:CSGN |
E484905
|
entity |
| Predicate | issuerStockExchangeCode |
P48660
|
FINISHED |
| Object | CSGN |
—
|
NE NERFINISHED |
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: CSGN | Statement: [SIX:CSGN, issuerStockExchangeCode, CSGN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CSGN Context triple: [SIX:CSGN, issuerStockExchangeCode, CSGN]
-
A.
CSGN
chosen
CSGN is the SIX Swiss Exchange ticker symbol for Credit Suisse Group, a major Swiss-based global financial services and investment banking firm.
-
B.
CGN
CGN is the IATA airport code for Cologne Bonn Airport, a major international airport serving the Cologne and Bonn region in western Germany.
-
C.
CGN
CGN is the National Rail station code for Cogan railway station in the Vale of Glamorgan, Wales.
-
D.
CGN
CGN is a Swiss company that operates passenger ferry and cruise services on Lake Geneva.
-
E.
CSG
CSG is the Commercial Stakeholder Group, a body representing commercial and business interests within the Internet Corporation for Assigned Names and Numbers (ICANN) policy development process.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 10, 2026, 1:35 p.m.