Triple
T12740061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for the Lira |
E304464
|
entity |
| Predicate | currencyStandard |
P35649
|
FINISHED |
| Object | gold-exchange standard |
—
|
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: gold-exchange standard | Statement: [Battle for the Lira, currencyStandard, gold-exchange standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyStandard Context triple: [Battle for the Lira, currencyStandard, gold-exchange standard]
-
A.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
B.
currency
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.
currencyFamily
chosen
Indicates that two currencies belong to the same broader monetary family or classification, typically sharing a common origin, standard, or structural framework.
-
D.
currencyCountry
Indicates that a given currency is officially used as legal tender in a particular country.
-
E.
currencyPractice
Indicates the customary or standard way a particular currency is used, represented, or managed in transactions or economic contexts.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.