Triple
T339177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian ruble (Empire) |
E6794
|
entity |
| Predicate | majorReform |
P4888
|
FINISHED |
| Object | 1839–1843 monetary reform |
—
|
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: 1839–1843 monetary reform | Statement: [Russian ruble (Empire), majorReform, 1839–1843 monetary reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorReform Context triple: [Russian ruble (Empire), majorReform, 1839–1843 monetary reform]
-
A.
reform
chosen
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
B.
notableReform
Indicates that an entity is recognized for having initiated, led, or been central to a significant reform or transformative change in a system, policy, or institution.
-
C.
constitutionalChange
Indicates a formal modification, addition, or removal of provisions within a constitution or foundational legal framework.
-
D.
majorIssue
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
E.
significantRevisionIn
Indicates that one entity represents a substantial or important change made within another entity, such as a major update or revision occurring in a larger work or version.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae3a27c81909fc7deb600125fb1 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.