Triple
T12616044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German–Spanish Treaty (1899) |
E301254
|
entity |
| Predicate | monetaryCompensationCurrency |
P245
|
FINISHED |
| Object | peseta |
—
|
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: peseta | Statement: [German–Spanish Treaty (1899), monetaryCompensationCurrency, peseta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryCompensationCurrency Context triple: [German–Spanish Treaty (1899), monetaryCompensationCurrency, peseta]
-
A.
currencyGiven
Indicates that one entity transfers or provides money or a monetary unit to another entity.
-
B.
monetaryUnitOfAccount
Indicates that something serves as the standard unit in which the value of goods, services, and financial transactions is measured and recorded.
-
C.
monetaryComponent
Indicates that something is a financial element or part of a larger monetary value, structure, or transaction.
-
D.
hasMonetaryComponent
Indicates that something includes, involves, or is associated with a monetary or financial element.
-
E.
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).
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:12 p.m.