Triple
T31600057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cruzeiro real |
E806325
|
entity |
| Predicate | precedesCurrency |
P3072
|
FINISHED |
| Object | real (Brazilian real) |
—
|
NE NERFINISHED |
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: real (Brazilian real) | Statement: [cruzeiro real, precedesCurrency, real (Brazilian real)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesCurrency Context triple: [cruzeiro real, precedesCurrency, real (Brazilian real)]
-
A.
previousCurrency
chosen
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
-
B.
successorCurrencyOf
Indicates that one currency has replaced another as the official or primary currency in use.
-
C.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
D.
precedesNumeral
Indicates that one numeral comes before another numeral in a specified ordering or sequence.
-
E.
usesCurrencyInitially
Indicates that an entity originally adopts or operates with a particular currency at the start of a defined period or process.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 30, 2026, 10:32 p.m.