Triple
T10414141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smithsonian Agreement |
E245472
|
entity |
| Predicate | limitedConvertibility |
P3714
|
FINISHED |
| Object | U.S. dollar into gold |
—
|
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: U.S. dollar into gold | Statement: [Smithsonian Agreement, limitedConvertibility, U.S. dollar into gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedConvertibility Context triple: [Smithsonian Agreement, limitedConvertibility, U.S. dollar into gold]
-
A.
convertibility
chosen
Indicates the capacity or possibility for one entity, state, or form to be changed or transformed into another.
-
B.
limitedIssueOf
Indicates that one entity is issued or made available in a restricted or finite quantity by another entity.
-
C.
convertibilityGuaranteedBy
Indicates that the ability to convert one asset, instrument, or value into another is assured or backed by a specified guarantor.
-
D.
limitedSystemType
Indicates that the system is restricted to a specific subset or category of system types, rather than allowing all possible types.
-
E.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0ec6fc8190a71af759226a3cba |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.