Triple
T5538552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese escudo |
E145229
|
entity |
| Predicate | euroAdoptionPhaseOutEnd |
P9579
|
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, euroAdoptionPhaseOutEnd, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: euroAdoptionPhaseOutEnd Context triple: [Portuguese escudo, euroAdoptionPhaseOutEnd, 2002]
-
A.
adoptedEuro
Indicates that a country or entity has officially adopted the euro as its legal currency.
-
B.
nonCashEuroChangeoverDate
Indicates the date on which the transition to the euro occurred for non-cash transactions (such as accounting and electronic payments).
-
C.
euroChangeoverCashDate
chosen
Indicates the date on which a country or region officially switched its physical cash currency to the euro.
-
D.
peggedToEuroSince
Indicates that the value of one currency or financial instrument has been fixed or tightly linked to the euro starting from a specific point in time.
-
E.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
- 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.