Triple
T15938224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | balance sheet recession theory |
E386492
|
entity |
| Predicate | keyCondition |
P7606
|
FINISHED |
| Object | near-zero nominal interest rates |
—
|
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: near-zero nominal interest rates | Statement: [balance sheet recession theory, keyCondition, near-zero nominal interest rates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyCondition Context triple: [balance sheet recession theory, keyCondition, near-zero nominal interest rates]
-
A.
keyRule
Indicates that a rule or principle functions as a key or primary governing condition for something.
-
B.
keyCol
Indicates that one column in a dataset or table serves as a key used to uniquely identify or link records.
-
C.
keyField
Indicates that the referenced field serves as a primary or unique identifier within a data structure or record.
-
D.
key
chosen
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
E.
keyDemand
Indicates that one entity requests or requires another entity to provide or use a specific key (such as a cryptographic or access key).
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.