Triple
T5850603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of 23 December 1865 |
E130019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | founding treaty of the Latin Monetary Union |
C88
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: founding treaty of the Latin Monetary Union Context triple: [Treaty of 23 December 1865, instanceOf, founding treaty of the Latin Monetary Union]
-
A.
currency union
A currency union is an agreement between two or more countries to share a common currency and monetary policy, typically managed by a joint central authority.
-
B.
proposed supranational currency unit
A proposed supranational currency unit is a theoretical monetary unit designed to function as a common medium of exchange and store of value across multiple sovereign nations, operating above and alongside their national currencies.
-
C.
fiat currency
A fiat currency is a government-issued form of money that has value primarily because a government maintains it and people have faith in its acceptance, rather than being backed by a physical commodity like gold or silver.
-
D.
economic and monetary union
An economic and monetary union is an integration arrangement in which participating countries coordinate economic policies, remove barriers to trade and capital movement, and adopt a common currency managed by a shared central monetary authority.
-
E.
founding treaty
chosen
A founding treaty is a formal, binding international agreement that establishes, constitutes, and defines the core structures, powers, and purposes of an international organization or political union.
- F. None of above.
Provenance (1 batch)
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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:55 p.m.