Triple
T3248388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somali shilling |
E68117
|
entity |
| Predicate | inflation |
P8010
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Somali shilling, inflation, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inflation Context triple: [Somali shilling, inflation, high]
-
A.
inflationType
Indicates the specific category or nature of inflation associated with an economic measure or context.
-
B.
inflationContext
Indicates that an event, statement, or value is interpreted specifically within the economic condition or period characterized by inflation.
-
C.
regulatesInflationWith
Indicates a relationship where one entity controls, influences, or stabilizes the inflation level of another entity, typically through specific tools, policies, or mechanisms.
-
D.
hasInflation
chosen
Indicates that an economic system, currency, or market is experiencing a general increase in prices and a corresponding decrease in purchasing power over time.
-
E.
inflationRateAfter
Indicates the rate of inflation that applies following a specified time, event, or reference point.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf3e9ed0819096ac238098ac403c |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.