Triple
T38247688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pounds & Dollars |
E1013936
|
entity |
| Predicate | currencyReferenced |
P245
|
FINISHED |
| Object | pound sterling |
—
|
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: pound sterling | Statement: [Pounds & Dollars, currencyReferenced, pound sterling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyReferenced Context triple: [Pounds & Dollars, currencyReferenced, pound sterling]
-
A.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
B.
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).
-
C.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
D.
currencyOversight
Indicates that an entity has authority or responsibility to supervise, regulate, or manage the use, issuance, or stability of a currency.
-
E.
currencyRetained
Indicates that a specified amount of currency is kept or held by an entity rather than spent, transferred, or released.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 3, 2026, 4:30 p.m.