Triple
T5538547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese escudo |
E145229
|
entity |
| Predicate | cashEuroChangeover |
P18112
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Portuguese escudo, cashEuroChangeover, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cashEuroChangeover Context triple: [Portuguese escudo, cashEuroChangeover, 2002]
-
A.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
B.
cashEuroIntroduction
chosen
Indicates the event or process in which euro banknotes and coins are first put into physical circulation as legal tender.
-
C.
fixedConversionRateToEuro
Indicates that one currency has a fixed, predetermined exchange rate relative to the euro.
-
D.
currencyPractice
Indicates the customary or standard way a particular currency is used, represented, or managed in transactions or economic contexts.
-
E.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fb2fe488190808e02ce5aabb2ad |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.