Triple
T19549229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pound Scots |
E489154
|
entity |
| Predicate | valueRelativeToPoundSterling |
P13470
|
FINISHED |
| Object | 1 pound sterling = 12 pounds Scots |
—
|
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: 1 pound sterling = 12 pounds Scots | Statement: [Pound Scots, valueRelativeToPoundSterling, 1 pound sterling = 12 pounds Scots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueRelativeToPoundSterling Context triple: [Pound Scots, valueRelativeToPoundSterling, 1 pound sterling = 12 pounds Scots]
-
A.
valueInUSD
Indicates that a given amount or asset is expressed or evaluated in terms of its monetary value in United States dollars (USD).
-
B.
valueInPence
Indicates the monetary amount of something expressed specifically in units of pence.
-
C.
valueInZloty
Indicates that one entity represents the monetary value of another entity expressed in Polish zloty (PLN).
-
D.
exchangeRateToPoundSterling
chosen
Indicates the rate at which one unit of a given currency can be converted into British pounds sterling.
-
E.
valueRelativeToAkçe
Indicates the value of something expressed in terms of, or relative to, the akçe monetary unit.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2f39188190976e8b6b111499a0 |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.