Triple
T22380553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States monetary system |
E553260
|
entity |
| Predicate | moneySupplyMeasures |
P147434
|
FINISHED |
| Object | M0 |
—
|
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: M0 | Statement: [United States monetary system, moneySupplyMeasures, M0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moneySupplyMeasures Context triple: [United States monetary system, moneySupplyMeasures, M0]
-
A.
regulatesMoneySupply
Indicates a relationship where one entity controls or influences the amount of money circulating within an economic or financial system.
-
B.
monetaryFunction
Indicates a relationship where something serves a financial role, such as handling, managing, or affecting money or economic value.
-
C.
monetaryHierarchy
Indicates a relationship where one entity holds a higher or lower monetary value, status, or priority relative to another within a structured financial ordering.
-
D.
monetarySystemType
Indicates the type or classification of a monetary system associated with an entity.
-
E.
definedMonetarySystem
Indicates that an authority or entity has established and specified the rules, structure, and characteristics of a particular monetary system.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582c05fc8190836ae008426177a5 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:45 p.m.