Triple
T17728129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Currency Act 1965 |
E442517
|
entity |
| Predicate | typeOfCurrency |
P11731
|
FINISHED |
| Object | decimal currency |
—
|
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: decimal currency | Statement: [Currency Act 1965, typeOfCurrency, decimal currency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCurrency Context triple: [Currency Act 1965, typeOfCurrency, decimal currency]
-
A.
currencyType
chosen
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
B.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
C.
currencyFamily
Indicates that two currencies belong to the same broader monetary family or classification, typically sharing a common origin, standard, or structural framework.
-
D.
currencyCodeDenoted
Indicates that a specific currency code is used to denote or represent a particular currency.
-
E.
currencySignAdopted
Indicates that a particular currency sign has been officially adopted for use with a given currency or monetary system.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e3cb708190b47456ad2008a65e |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.