Triple
T9575192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plano Real |
E231027
|
entity |
| Predicate | currencyCodeIntroduced |
P49870
|
FINISHED |
| Object | BRL |
—
|
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: BRL | Statement: [Plano Real, currencyCodeIntroduced, BRL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyCodeIntroduced Context triple: [Plano Real, currencyCodeIntroduced, BRL]
-
A.
introducedAsCurrency
chosen
Indicates that something was formally established or adopted for use as a medium of exchange (money) within an economy or system.
-
B.
reintroducedCurrencyOf
Indicates that a currency has been brought back into use as legal tender in a particular country or region after having been previously replaced, discontinued, or suspended.
-
C.
legalTenderSince
Indicates the point in time from which something has officially held the status of legal tender within a given jurisdiction.
-
D.
isLegalTenderSince
Indicates that something has held the status of legal tender starting from a specified point in time.
-
E.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99aa964c8190a50717edff30f10b |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.