Triple
T31600132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plano Verão |
E806327
|
entity |
| Predicate | currencyConversionRate |
P92667
|
FINISHED |
| Object | 1000 Cruzados = 1 Cruzado Novo |
—
|
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: 1000 Cruzados = 1 Cruzado Novo | Statement: [Plano Verão, currencyConversionRate, 1000 Cruzados = 1 Cruzado Novo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyConversionRate Context triple: [Plano Verão, currencyConversionRate, 1000 Cruzados = 1 Cruzado Novo]
-
A.
currencyExchangeRate
chosen
Indicates the rate at which one currency can be exchanged for another.
-
B.
exchangeCurrency
Indicates a relationship where one party converts or trades an amount of one currency for an equivalent amount of another currency.
-
C.
hasCurrencyConverter
Indicates that one entity provides or includes a mechanism to convert values between different currencies for another entity.
-
D.
exchangeRateToPoundSterling
Indicates the rate at which one unit of a given currency can be converted into British pounds sterling.
-
E.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
- 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_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 30, 2026, 10:32 p.m.