Triple
T99747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcker shock |
E2014
|
entity |
| Predicate | underlyingTheory |
P533
|
FINISHED |
| Object | monetarism |
—
|
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: monetarism | Statement: [Volcker shock, underlyingTheory, monetarism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingTheory Context triple: [Volcker shock, underlyingTheory, monetarism]
-
A.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
B.
implementedUnder
Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing entity.
-
C.
ontologicalAspect
Indicates a fundamental mode or category of being that characterizes how something exists or is realized.
-
D.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
E.
coreIdea
chosen
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a253b95d4c81909d1f2bc37e799c44 |
completed | Feb. 28, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69a24ebfc5a88190bdd1653b9fa541fe |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.