Triple
T31293907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitchells & Butlers plc |
E798022
|
entity |
| Predicate | securityCurrency |
P245
|
FINISHED |
| Object | GBP |
—
|
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: GBP | Statement: [Mitchells & Butlers plc, securityCurrency, GBP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityCurrency Context triple: [Mitchells & Butlers plc, securityCurrency, GBP]
-
A.
currency
chosen
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
B.
safeHavenCurrency
Indicates a currency that tends to retain or increase its value during periods of market stress or economic uncertainty, attracting investors seeking lower risk.
-
C.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
D.
currencyOversight
Indicates that an entity has authority or responsibility to supervise, regulate, or manage the use, issuance, or stability of a currency.
-
E.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 9:14 p.m.