Triple
T24648211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InterContinental Hotels Group plc |
E610172
|
entity |
| Predicate | tickerOnLSE |
P1447
|
FINISHED |
| Object | IHG |
—
|
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: IHG | Statement: [InterContinental Hotels Group plc, tickerOnLSE, IHG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tickerOnLSE Context triple: [InterContinental Hotels Group plc, tickerOnLSE, IHG]
-
A.
issuerHasLSESegment
Indicates that an issuer is associated with, or listed on, a specific segment of the London Stock Exchange (LSE).
-
B.
tickerSymbol
chosen
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
-
C.
stockExchangeStatus
Indicates the operational or trading condition of a stock exchange at a given time (e.g., open, closed, halted).
-
D.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
E.
mainStockExchangeOf
Indicates that one entity serves as the primary stock exchange on which the other entity (typically a company or financial instrument) is chiefly listed or traded.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:33 a.m.