Triple
T29393514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franc |
E745432
|
entity |
| Predicate | statusInEurozone |
P193541
|
FINISHED |
| Object | Replaced by euro |
—
|
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: Replaced by euro | Statement: [Franc, statusInEurozone, Replaced by euro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInEurozone Context triple: [Franc, statusInEurozone, Replaced by euro]
-
A.
locatedInEurozone
Indicates that the subject entity is situated within the geographic or economic area of the Eurozone.
-
B.
europeanUnionStatus
Indicates whether an entity is a member of, associated with, or otherwise holds a defined status in relation to the European Union.
-
C.
eurozoneMember
Indicates that an entity is a country that belongs to the Eurozone, i.e., it uses the euro as its official currency within the European Union’s monetary union.
-
D.
euroParticipation
Indicates that an entity takes part in or is involved with the Euro currency system or Eurozone monetary framework.
-
E.
statusOfEuropeanDepositInsuranceScheme
Indicates the current state or condition of a European Deposit Insurance Scheme within a given context or timeframe.
- F. None of above. chosen
Provenance (4 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: April 28, 2026, 2:44 p.m.