Triple
T31600434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cruzado |
E806334
|
entity |
| Predicate | replacedByCurrencyAtRate |
P6186
|
FINISHED |
| Object | 1 cruzado novo = 1,000 cruzados |
—
|
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 cruzado novo = 1,000 cruzados | Statement: [cruzado, replacedByCurrencyAtRate, 1 cruzado novo = 1,000 cruzados]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByCurrencyAtRate Context triple: [cruzado, replacedByCurrencyAtRate, 1 cruzado novo = 1,000 cruzados]
-
A.
replacedCurrencyAtRate
chosen
Indicates that one currency was substituted for another at a specified exchange rate.
-
B.
replacedCurrencyRate
Indicates that one currency exchange rate has been superseded or substituted by another rate in a given context.
-
C.
replacedCurrencyDate
Indicates the date on which one currency was officially replaced by another.
-
D.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
E.
replacedCurrencyCode
Indicates that one currency has been superseded or replaced by another currency, identified by its code.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 30, 2026, 10:32 p.m.