Triple
T2081857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian real |
E45260
|
entity |
| Predicate | currentBanknoteDenomination |
P2871
|
FINISHED |
| Object | 2 reais |
—
|
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: 2 reais | Statement: [Brazilian real, currentBanknoteDenomination, 2 reais]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentBanknoteDenomination Context triple: [Brazilian real, currentBanknoteDenomination, 2 reais]
-
A.
banknoteDenomination
chosen
Indicates the specific face value assigned to a banknote in a given currency.
-
B.
currentBanknoteSeries
Indicates that the subject is part of, or associated with, the banknote series that is currently in official circulation.
-
C.
typeOfBanknotes
Indicates a relationship where one entity specifies the kind or category of banknotes associated with another entity.
-
D.
currencyOfDenomination
Indicates that one currency unit is a specific denomination or face value within another currency system.
-
E.
frequentlyUsedBanknotes
Indicates that the referenced banknotes are commonly or regularly used in transactions within a given context 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba35c2588190933dba882f52dd17 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.