Triple
T3388587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurosystem |
E71361
|
entity |
| Predicate | usesPolicyRate |
P47179
|
FINISHED |
| Object | main refinancing operations rate |
—
|
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: main refinancing operations rate | Statement: [Eurosystem, usesPolicyRate, main refinancing operations rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPolicyRate Context triple: [Eurosystem, usesPolicyRate, main refinancing operations rate]
-
A.
feePolicy
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
B.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
-
C.
negotiatedUnderPolicy
Indicates that an agreement or arrangement was reached through a negotiation process conducted in accordance with a specific policy or set of policy rules.
-
D.
usesMaterialsPolicy
Indicates that an entity follows, applies, or is governed by a specified policy regarding the use of materials.
-
E.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb665c6008190b33994ef20f5bd61 |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69ada43615f08190ac2275020d157983 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada527ff308190813a7ffdcdec4322 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.